We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Currently the files are downloaded to the file browser, and saved in the web browser storage (indexed DB).
After discussion with @martinRenou, we could probably use a custom drive instead of copying the files to the file browser.
Advantages / drawbacks to be discussed.
The text was updated successfully, but these errors were encountered:
and saved in the web browser storage (indexed DB).
When used in JupyterLite, right? I suppose because by default JupyterLite saves files in IndexedDB.
This could also be relevant to jupyterlite/jupyterlite#1041, if this behavior gets moved to a drive at some point too.
Sorry, something went wrong.
When used in JupyterLite, right?
Right, if this extension was installed on a classic JupyterLab session, you would download the entire git repo onto the server
No branches or pull requests
Currently the files are downloaded to the file browser, and saved in the web browser storage (indexed DB).
After discussion with @martinRenou, we could probably use a custom drive instead of copying the files to the file browser.
Advantages / drawbacks to be discussed.
The text was updated successfully, but these errors were encountered: