Updates in AI preferences panel#2157
Merged
Merged
Conversation
…here Note that sound might have preference overrides in some situations (now or in the future), so therefore it is better not to add the preference at the user level in the API
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.
Issue(s)
#2073
Description
This PR incorporates improvements in the Generative AI preferences panel as discussed in the issue above. Main changes are:
What this PR does not include is the possibility of overriding user preferences on a per-sound basis (except for the voice case). If this becomes a necessity, we could add an extra field in the sound description form or use a tag like "no-gen-ai" that will be used to override global settings.
Deployment steps:
This PR needs to run the
migratecommand after it is deployed.The relevant text in FAQ should be updated to the one below: