Skip to content

Auto save/backup when Output changes #100329

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

Closed
DonJayamanne opened this issue Jun 16, 2020 · 0 comments
Closed

Auto save/backup when Output changes #100329

DonJayamanne opened this issue Jun 16, 2020 · 0 comments
Labels
insiders-released Patch has been released in VS Code Insiders

Comments

@DonJayamanne
Copy link
Contributor

DonJayamanne commented Jun 16, 2020

When user executes cells in a notebook, the output changes, at this point the Notebook should be changed.

At the end of the day output is part of the Notebook Document stored on disc.

Similarly, if the execution order changes or similar metadata changes, the document should be saved.

Challenges
I guess we'll need to determine what metadata contributes to saving a notebook document, or more specifically what metadata can be stored in a document. Technically all metadata can be stored in a physical file, hence if any metadata changes, then document must be saved to disc.

However, making a cell runnable/editable doesn't necessarily have to be saved to disc, at least not in the case of Jupyter notebooks.

Alternate solution - extension can be responsible for performing the save/backup as and when it sees fit.

@rebornix /cc

@github-actions github-actions bot locked and limited conversation to collaborators Aug 2, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
insiders-released Patch has been released in VS Code Insiders
Projects
None yet
Development

No branches or pull requests

2 participants
@DonJayamanne and others