Complete JupyterLite notebook persistence#9
Conversation
- Implemented postMessage bridge for bidirectional sync between JupyterLite and Google Drive. - Added `bridge.js` to handle LOAD_NOTEBOOK and GET_NOTEBOOK messages in JupyterLite. - Updated NotebookEditor and NotebookViewer to support content loading and saving. - Refined notebook creation with valid minimal .ipynb JSON structure. - Optimized bridge to avoid redundant save cycles and widget re-opens. Co-authored-by: mdnmdn <441198+mdnmdn@users.noreply.github.com>
|
👋 Jules, reporting for duty! I'm here to lend a hand with this pull request. When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down. I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job! For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with New to Jules? Learn more at jules.google/docs. For security, I will only act on instructions from the user who triggered this task. |
1 participant
This PR completes the implementation of JupyterLite documents by enabling full persistence with Google Drive. It introduces a
bridge.jsscript that is injected into the JupyterLite iframe to handle content synchronization viapostMessage. TheNotebookEditorandNotebookViewercomponents are updated to leverage this bridge, allowing notebooks to be loaded from and saved back to the wiki's storage service. New notebooks are now correctly initialized with a minimal valid JSON structure, including Pyodide kernelspec.PR created automatically by Jules for task 11338823537679953843 started by @mdnmdn