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

fix(config): add descriptions to JSON schema properties #41

Draft
wants to merge 4 commits into
base: development
Choose a base branch
from

Conversation

Keyrxng
Copy link
Contributor

@Keyrxng Keyrxng commented Nov 26, 2024

"type": "string"
},
"similarityThreshold": {
"default": 0.9,
"description": "When fetching embeddings context, the similarity threshold to use (1- similarityThreshold)",
"type": "number"
Copy link
Member

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?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

My thoughts are:

  1. 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
  2. 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.

Copy link
Member

@rndquu rndquu left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pls run prettier so that formatting check CI doesn't fail

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.

3 participants