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

Saving Notebooks when multiple editors for same notebook are opened #97280

Closed
DonJayamanne opened this issue May 8, 2020 · 1 comment
Closed
Assignees
Labels
notebook under-discussion Issue is under discussion for relevance, priority, approach

Comments

@DonJayamanne
Copy link
Contributor

DonJayamanne commented May 8, 2020

Widgets in Jupyter Notebooks have state in them.
It is possible to save a Jupyter notebook with the state information in the ipynb file.
This way, when the ipynb file is opened, the widget state is available and it can be rendered (even without a real kernel).

Saving widget an nb with widget state is optional, and we as extension authors can some how prompt/determine whether this additional information needs to be saved or not.

However, if a user has multiple editors for the same notebook opened, then its possible the widget state on both are completely different.

Possible solution

  • Allow extension the ability to control whether a notebook document can be opened multiple times or not (doesn't feels like a solution, more of a bandaid)
    • Then again, the custom editor supports this as well, I guess this is a valid solution.

@rebornix /cc

@rebornix rebornix added notebook under-discussion Issue is under discussion for relevance, priority, approach labels Jun 2, 2020
@DonJayamanne
Copy link
Contributor Author

DonJayamanne commented Jun 15, 2020

Closing as this has been discussed with @rebornix

@github-actions github-actions bot locked and limited conversation to collaborators Jul 30, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
notebook under-discussion Issue is under discussion for relevance, priority, approach
Projects
None yet
Development

No branches or pull requests

2 participants