Lock chat default directory #6
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
brichet
force-pushed
the
lock_chat_default_directory
branch
from
2e0c878 to
5f20a76
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR lock the settings for the chat files' default directory.
It depend on jupyterlab/jupyter-chat#91 to be merged and released.
Motivations
The left panel look for chat files in one directory only, to avoid overload at startup in case of large file system.
This PR is a way of “abstracting” the chat files for AI users, ensuring that all chats are created in a single directory, for all collaborators.
Discussion
Some may want chat files to be stored with other project-related files.
In this case we should rethink Chats directory config jupyterlab/jupyter-chat#91, to handle chats files in the whole tree file.
Using a hidden directory to abstract a bit more the chats
This seems to not be possible by default. Accessing hidden directory from the frontend require to enable it on the server application
--ContentsManager.allow_hidden=true