-
Notifications
You must be signed in to change notification settings - Fork 29.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove the notebookContentProvider API proposal #147248
Comments
@mjbvz here is an update: #125757 (comment) |
@alyssajotice How's Liveshare's migration been going? Run into any blockers or have any questions? |
Hey @mjbvz, I am currently working on the design docs for this. This will be a large, three-part change to the Live Share notebooks architecture, and our goal is to have this done by the fall. I'll send you the design doc when it is complete so you can stay up to date. |
For microsoft#147248 Marks the top level types in this file as deprecated. Also hooks up `registerNotebookContentProvider` to report deprecated API usage
For #147248 Marks the top level types in this file as deprecated. Also hooks up `registerNotebookContentProvider` to report deprecated API usage
Looks like liveshare is not using |
For microsoft#147248 When stepping through the liveshare code, we figured out they do not appear to be using `save`, `saveAs`, or `backup` (they return empty results for these) This PR removes this part of the proposal so we can track just the parts of the api that they are using
For #147248 When stepping through the liveshare code, we figured out they do not appear to be using `save`, `saveAs`, or `backup` (they return empty results for these) This PR removes this part of the proposal so we can track just the parts of the api that they are using
All external consumers have now migrated off this api We just need to move our tests off of this api and then we can remove it entirely: #160580 |
The
notebookContentProvider
API proposal is currently not on track for finalization. This api was introduced when we were still figuring out the model for working with notebooks and was inspired by the custom editor api. However we ultimately went with the much simplerNotebookSerializer
APIParts of the
notebookContentProvider
API are not well tested or supported today and maintaining it adds complexity to VS Code. We'd like to remove it, however the API is currently used by (or at least enabled for):Please let us know if/how you are using the
notebookContentProvider
api and if there are any factors that would block you from migrating off of itThe text was updated successfully, but these errors were encountered: