-
Notifications
You must be signed in to change notification settings - Fork 8
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
fix(config): add descriptions to JSON schema properties #41
base: development
Are you sure you want to change the base?
fix(config): add descriptions to JSON schema properties #41
Conversation
"type": "string" | ||
}, | ||
"similarityThreshold": { | ||
"default": 0.9, | ||
"description": "When fetching embeddings context, the similarity threshold to use (1- similarityThreshold)", | ||
"type": "number" |
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.
Do we want some examples for similarityThreshold and maxTokens? Or do you use that only for the values that have no default?
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.
My thoughts are:
- If it's obvious and the
input
is filled with the value type (number in this case) then it's pointless and would look silly - If the value is simple and displayed within the description then again no need for a example
These are planned to be displayed above/below the input areas like
When fetching embeddings context...
Examples: [<examples in this array>]
Something like that but within the tooltip. So the user would see how to write this prop 3 different times if we also included examples
because it exists in the description and input
ele.
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.
Relates to ubiquity-os/ubiquity-os-plugin-installer#24