Remove Notebook API support

[andyleejordan]

The Notebook API support was partially implemented but based on early Visual Studio Code APIs which have yet to be finalized. Since our support is experimental, it probably ought to have been in a feature branch. So we're planning to:

• Turn off the GitHub actions which open new PRs updating our use of the experimental APIs
• Remove the Notebook code from the extension itself
• Save the prototype in a feature branch to be revisited in the future

/cc @TylerLeonhardt @rjmholt @SydneyhSmith

[rjmholt]

Yeah I think the key issue for us is that we had assumed the VSCode notebook APIs would stabilise sooner than it has, so it was acceptable to take the incremental changes in the meantime.

We've proven the concept (and helped VSCode develop their API), but managing the update PRs has become an ongoing burden — the simplest solution is for us to wait for the API to be exposed stably by VSCode and then to re-enable our notebook integration code.

[andyleejordan]

That "feature branch" is just the fact that it's in the history as a merged PR 😅

[dkattan]

Damn, I was just sitting down to finally play with this lol.

[andyleejordan]

It'll come back one day! Just when the VS Code API is stable and we can integrate with it properly. For now, we're focussing on much-needed stabilization work for the extension. 😄

[janegilring]

What are the current status of the VS Code API and plans to integrate the Notebook API?

[ghost]

Thank you for your comment, but please note that this issue has been closed for over a week. For better visibility, consider opening a new issue with a link to this instead.