Implement high fidelity designs for navbar, summary/transcription, conversations, and chat pages#47
Merged
Merged
Conversation
when you collapse the chat, the collapsed bar is grey until you move the mouse again. this is because it was saving the color from when the cursor hovered over the collapsed bar and clicked on it
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
jasutiin
changed the title
there was a bug where i made a chat with 0 linked conversations, and it made a new chat. however, there was no way to navigate back to the main chat page to create a new chat, because it defaulted to going to that general chat that i made. this has been fixed
…-transcription-convo-chat
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
2 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.
This is the combination of #45 and #46.
This update makes the chat system use shared persisted chat threads instead of treating the dashboard chat page and the conversation-level chat as separate histories.
Backend-wise, the main change is in
chat.tsandschema.ts. The existingchatMessagestable is now used as a thread-backed store by introducing a thread key concept on top of the current per-message records. A chat thread is resolved deterministically from the selected conversation context:That design is what prevents duplication. If a user starts a chat from an individual conversation page, that history is stored against that conversation’s thread and will also appear in the dashboard chat page history. Likewise, if the user links exactly one conversation inside the dashboard chat page, the app reuses that same underlying thread instead of creating a second copy of the conversation chat. If the user links two or more conversations, the resulting thread is chat-page-only and does not overwrite or replace the individual chat history for any of those conversations.