Skip to content
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

🌿 feat: Multi-response Streaming #3191

Merged
merged 48 commits into from
Jun 25, 2024
Merged

🌿 feat: Multi-response Streaming #3191

merged 48 commits into from
Jun 25, 2024

Conversation

danny-avila
Copy link
Owner

@danny-avila danny-avila commented Jun 25, 2024

Summary

Closes #3028

Adds ability to message two different endpoints/models/presets at once.

image

You can use the "+" text command to add a second response setting, or simply click on the "+" button now found in the Header.

image
image
image

You can select which response to reply to, allowing you to navigate the conversation with the preferred response

image

Other Changes

  • In order to achieve the above, a major refactor for making new generation requests, managing conversation state, and message rendering were necessary
  • Messages also now describe their depth when rendered
  • added dev mode browser console logger (minimal implementation)
  • optimized rendering for user message icons
  • fixed an issue where regenerations/edits in a new chat with an image attached would not recognize the image
  • Updated footer to use the new slogan
  • remove info level of logs in favor of debug level for GoogleClient
  • fixed an issue discovered with aborting message requests

Change Type

  • New feature (non-breaking change which adds functionality)

Checklist

  • My code adheres to this project's style guidelines
  • I have performed a self-review of my own code
  • I have commented in any complex areas of my code
  • I have made pertinent documentation changes
  • My changes do not introduce new warnings
  • I have written tests demonstrating that my changes are effective or that my feature works
  • Local unit tests pass with my changes
  • Any changes dependent on mine have been merged and published in downstream modules.
  • A pull request for updating the documentation has been submitted.

refactor: pass newConversation to Mention component

refactor: useChatFunctions for modular use of `ask` and `regenerate`

refactor: set latest message only for the first index in useChatFunctions

refactor: pass setLatestMessage to useChatFunctions

refactor: Pass setSubmission to useChatFunctions for submission handling

refactor: consolidate event handlers to separate hook from useSSE

WIP: additional response handlers

feat: responsive added convo, clears on new chat/navigating to chat, assistants excluded

feat: Add conversationByKeySelector to select any conversation by index

WIP: handle second submission with messages paired to root
@danny-avila danny-avila merged commit 156c52e into main Jun 25, 2024
4 checks passed
@danny-avila danny-avila deleted the feat/multi-res branch June 25, 2024 07:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Enhancement: Multiple Response Streaming
1 participant