You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'd like to propose a feature request to align the underlying JSON structure of the .vsnb files (or the equivalent file format used by this official extension) more closely with the standard Jupyter Notebook (.ipynb) format.
It appears that this official Wolfram Language VS Code extension may have adopted the same JSON file format used by the community extension Wolfram Language Notebook by njpipeorgan.
I recently made a detailed suggestion for this format alignment on the GitHub issues page for that extension, outlining the benefits for interoperability, sharing, future-proofing, and simplified conversion. You can find my detailed motivation and discussion for this suggestion HERE.
Adopting the Jupyter key names (e.g., cell_type, source) and including standard Jupyter notebook metadata (like metadata.language_info) would make notebooks created with this official extension more broadly compatible with the extensive Jupyter ecosystem, while still leveraging the excellent VS Code native notebook experience you provide.