-
Notifications
You must be signed in to change notification settings - Fork 640
Feature/chatbot secrets compatibility #622
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
base: main
Are you sure you want to change the base?
Feature/chatbot secrets compatibility #622
Conversation
Merged with upstream
Merging fork with local
…ure/chatbot-secrets-compatibility
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@joshlavroff looks great. Can you cherry pick the relevant commits and move them to a new branch? This PR includes already merged/closed commits from weeks ago. After that, will be good to merge!
@joshlavroff also, can you attach a screen recording as well? |
@shivam-singhal Yes I've just opened a new PR with these fixes #630 |
6ac1dad
to
bdb2c4e
Compare
name: Pull Request
about: Create a pull request to contribute to the project
title: ''
labels: ''
assignees: ''
Description of Changes
API keys for the chat component can now be loaded from a project's
secrets.toml
file. Keys that are entered during a session are not saved and will remain only in the sessionStorage until the app is closed.Type of Change
Testing
Code has been tested against the currently present chat example in the Iris example project.
Checklist