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
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.
Summary
Refactor the frontend workspace layout and sidebar navigation to improve module ownership, code organization, interaction consistency, and maintainability without changing existing APIs or user workflows.
Key changes:
entities/conversation, including sidebar state, conversation list rules, sharing, and export behavior.Change type
Affected areas
Verification
cd frontend && pnpm lintcd frontend && pnpm buildgit diff --checkScreenshots, API examples, or logs
Sidebar UI was manually reviewed in both expanded and collapsed states, including:
No API request or response changes are included.
Configuration, migration, and compatibility notes
No environment variables, database schema, deployment configuration, public URLs, or backend API contracts were changed.
The changes reorganize internal frontend module ownership and imports. Existing routes, authentication guards, conversation operations, and user-facing workflows remain compatible.
Documentation
Security and privacy
Checklist
.pycfiles,.envfiles, and local storage data are not committed.