Skip to content
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

Notebook API evolution #106744

Closed
jrieken opened this issue Sep 15, 2020 · 1 comment
Closed

Notebook API evolution #106744

jrieken opened this issue Sep 15, 2020 · 1 comment
Assignees
Labels
api notebook plan-item VS Code - planned item for upcoming

Comments

@jrieken
Copy link
Member

jrieken commented Sep 15, 2020

This issue is a high level summary of all notebook API discussions. It should provide an overview of how stable or unstable certain areas of the API are and where to expect major or minor changes.

Issues labeled with notebook and api are on our radar https://github.com/microsoft/vscode/issues?q=is%3Aopen+label%3Anotebook+label%3Aapi. The following is a subset of those issues grouped by the area into which they fall

Notebook execution

Notebook output

[Notebook|Cell]-Metadata

NotebookEditor

@microsoft microsoft locked as off-topic and limited conversation to collaborators Sep 15, 2020
@jrieken jrieken added the under-discussion Issue is under discussion for relevance, priority, approach label Sep 15, 2020
@jrieken jrieken changed the title Notebook API review Notebook API evolution Sep 15, 2020
@jrieken jrieken added plan-item VS Code - planned item for upcoming and removed under-discussion Issue is under discussion for relevance, priority, approach labels Nov 10, 2020
@jrieken
Copy link
Member Author

jrieken commented Mar 31, 2021

Closing - this is just a snapshot and has gone stale

@jrieken jrieken closed this as completed Mar 31, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
api notebook plan-item VS Code - planned item for upcoming
Projects
None yet
Development

No branches or pull requests

4 participants