-
Notifications
You must be signed in to change notification settings - Fork 14
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
Integrate jupyterlab-unfold into JupyterLab core #57
Comments
Thanks for your suggestion!
Even though I would be 👍🏽 for this myself, I believe this may be too much of an opinionated change that some users may not like. We could make it configurable though, to be able to switch easily between one or the other? |
I'm OK with making it configurable; hopefully, a configuration option won't introduce too much added complexity. |
Being able to use both would be great. Adding Also some users might still prefer the current lab file browser, for example in the case of Notebook. |
FYI I've added jupyterlab/jupyterlab#5526 to the |
+1 on having this available as part of core, with a user preference for selecting which view is offered (the current file listing view is no less opinionated...). In an education setting, novices don't necessarily have an understanding of file paths, and being able to have a global view of the directory structure can save them from losing track of where files are. (That said, the current directory view has the benefit of "if you can't see it, you'll need a path in your code to locate it" if the directory view follows the home of the selected notebook) |
This is related to jupyterlab/jupyterlab#5526, as discussed at the 2024-09-04 Jupyter frontends meeting.
Several JupyterLab users have expressed a desire to have a file browser with expandable folders in the left panel, for feature parity with other IDEs, such as Visual Studio Code. Would it be possible to merge this extension into JupyterLab core, replacing the behavior of the standard filebrowser, which displays one folder at a time?
The text was updated successfully, but these errors were encountered: