-
Notifications
You must be signed in to change notification settings - Fork 31
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
Feature/add settings to chat model #1027
Merged
gecBurton
merged 12 commits into
feature/llm-selector
from
feature/add-settings-to-chat-model
Sep 9, 2024
Merged
Feature/add settings to chat model #1027
gecBurton
merged 12 commits into
feature/llm-selector
from
feature/add-settings-to-chat-model
Sep 9, 2024
Conversation
This file contains 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
gecBurton
force-pushed
the
feature/add-settings-to-chat-model
branch
from
September 7, 2024 18:48
13975f2
to
efa0d4a
Compare
gecBurton
force-pushed
the
feature/llm-selector
branch
from
September 7, 2024 18:49
dab8fba
to
a6c20e8
Compare
gecBurton
commented
Sep 9, 2024
user: User = self.scope.get("user", None) | ||
user: User = self.scope.get("user") | ||
chat_backend = data.get("llm") | ||
temperature = data.get("temperature") |
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.
this will default to None
, i.e. the frontend does not need to set this
KevinEtchells
approved these changes
Sep 9, 2024
KevinEtchells
added a commit
that referenced
this pull request
Sep 9, 2024
* added ai-settings to chat model * added migration test * simplified * Add LLM selector to the UI * Send selected LLM back to Django (via form submit and websocket) * Explicitly set value attributes on LLM selector, so "(default)" isn't passed on * pasing values to front end * reduced the scale of change * now updating * added temprature * added temperature to consumer --------- Co-authored-by: George Burton <g.e.c.cburton@gmail.com> Co-authored-by: Kevin Etchells <kevetchells@hotmail.com>
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.
Context
I want the front end LLM sector to actually change the chat_backend, this will be "stuck" to the
Chat
objectChanges proposed in this pull request
AbstractAISettings
created, this has all thechat_backend
field asAISettings
.AISettings
inherits fromAbstractAISettings
(i.e. no change)Chat
now also inherits fromAbstractAISettings
Chat.chat_backend
instances are back populated with the relevantAISettings.chat_backend
valuesChat.save
is modified to populate thechat_backend
fields fromchat.user.ai_settings
Guidance to review
Relevant links
Things to check