468 Implement User-Specific Chat Sessions for Workspaces #515
Conversation
This file contains hidden or 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
# Conflicts: # server/models/threadChats.js
|
What's the update on this? 😭 Desperately need it. |
|
It is a must for any LLM Chat! |
|
Any updates on this pull requests? |
|
This is epic!!!! Thank for making this. Extremely grateful! |
10 tasks
Member
|
Due to merge conflicts and automatic compatibility with existing AnythingLLM versions, this feature is being moved to #699. @self-programming-bio-robot Ping me if in Discord & would like a contributor badge. While we couldn't use the existing version of this PR, you did accomplish this feature and were the catalyst for its execution into @nitchevcasseus @rpol @colakang @ThomasEwing04 Please follow the preceding issue. Should be merged tomorrow, at worst Monday next week - promise |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
6 participants
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.
Hello everyone!
Firstly, I apologize for the extensive size of this pull request. These changes were initially developed for my own purposes.
I'm excited to share this new pull request that introduces a significant enhancement to our workspace functionality. This update is in response to the feature request for allowing users to create, manage, and navigate separate chat sessions within each workspace. Here's what this PR accomplishes:
Key Additions:
Database Schema Update: Added a new thread model to our database schema to support separate chat sessions.
Data Migration: Developed a migration script that seamlessly integrates existing data into the new schema without any loss of information.
API Enhancements: Implemented a set of APIs to handle operations like retrieving, creating, updating, and deleting chat threads.
UI Integration: Introduced a new UI block in the sidebar for thread management. This includes functionalities like creating new threads, renaming them. I've made sure to align these changes with the existing chat paths.
Notes for Reviewers:
Testing and Feedback:
I've thoroughly tested these changes to ensure functionality and reliability. However, additional testing and feedback are always welcome. If you encounter any issues or have suggestions for further improvement, please feel free to share.
Thank you for taking the time to review this PR. I look forward to your valuable inputs and collaboration in refining this feature.
P.S. Should you decide to migrate to a different provider, such as PostgreSQL, please exercise caution with the migration script. I've crafted a specific block for migrating legacy data. Feel free to copy this block into your migration scripts.