Settings for controlling if outputs should be saved to disk

Originally filed here by @rebornix https://github.com/microsoft/vscode-jupyter/issues/4670

I think we should consider adding this feature into VSCode. I’ve implemented this same feature in Kusto notebooks. Feels like something generic for VS Code.

Similar to having a cell toolbar position per viewtype, we can have Save Notebook Outputs per viewtype. This can be achieved easily from VS Code by passing an empty array into the serializer, when saving notebooks.

I personally think this would be useful for rest notebooks as well, one might want the output from the REST & GithubIssues Notebook to be saved in the notebook, just like kusto notebooks (some might want the charts/data & some might not).

Thus all notebooks can be considered serializable (including output for sharing) & user choses whether the output is to be persisted on disc or not.

E.g. with .NET team building their notebook format (*.dib) this would have to be impelemented yet again in their extension.

@rebornix /cc

[MrNickArcher]

I came looking for this. Sad to see it hasn’t got much enthusiasm. I also want it

• Preparing notebooks for teaching without accidentally giving students any pre-run outputs
• Hiding sensitive output and metadata when committing to git repositories

[andreaschiappacasse]

+1 This would be also super useful in managing version control of .ipynb, in order to avoid committing large outputs/sesntive output which may be generated by the notebook.