fix(config): add descriptions to JSON schema properties

[Keyrxng]

Relates to ubiquity-os/ubiquity-os-plugin-installer#24

[rndquu]

@Keyrxng Regarding PRs:

• fix(config): add descriptions to JSON schema properties daemon-pricing#56
• fix(config): add descriptions to JSON schema properties #94
• fix(config): add descriptions to JSON schema properties command-query#25
• fix(config): add descriptions to JSON schema properties daemon-disqualifier#52
• fix(config): add descriptions to JSON schema properties command-ask#41
• fix(config): add descriptions to JSON schema properties text-vector-embeddings#49
• fix(config): add descriptions to JSON schema properties command-wallet#24
• fix(config): add descriptions to JSON schema properties daemon-merging#30

Could you add parameter examples in the parameter descriptions? Otherwise it's really hard for a partner to grasp what exact values the parameters accept.

[Keyrxng]

@Keyrxng Regarding PRs:

• fix(config): add descriptions to JSON schema properties daemon-pricing#56
• fix(config): add descriptions to JSON schema properties #94
• fix(config): add descriptions to JSON schema properties command-query#25
• fix(config): add descriptions to JSON schema properties daemon-disqualifier#52
• fix(config): add descriptions to JSON schema properties command-ask#41
• fix(config): add descriptions to JSON schema properties text-vector-embeddings#49
• fix(config): add descriptions to JSON schema properties command-wallet#24
• fix(config): add descriptions to JSON schema properties daemon-merging#30

Could you add parameter examples in the parameter descriptions? Otherwise it's really hard for a partner to grasp what exact values the parameters accept.

Sure, and this example should be displayed inside the tooltip as well?? I don't think it'll be effective to use them as "placeholders" for input areas since we fill those with either A) defaults B) their installed config.

[rndquu]

Sure, and this example should be displayed inside the tooltip as well??

Yes

I don't think it'll be effective to use them as "placeholders" for input areas since we fill those with either A) defaults B) their installed config.

You mean showing examples in the description is not effective?

[Keyrxng]

You mean showing examples in the description is not effective?

No I meant input.placeholder like the background text of input, textarea and things like that.

Sure, and this example should be displayed inside the tooltip as well??

Yes

Yeah no problem

[Keyrxng]

Some props don't require an example as they are either:

• boolean
• self-explanatory through either it's name, default or description such as emptyWalletText

All have been updated that need an example now

[rndquu]

@Keyrxng The examples key is automatically placed in the manifest, correct?

[Keyrxng]

Yeah https://github.com/ubiquity-os-marketplace/command-start-stop/blob/development/.github/workflows/update-configuration.yml uses https://github.com/ubiquity-os/action-deploy-plugin/blob/e97f622804cc2a1b802ebdb99d640b3293af72d8/action.yml#L134 which should inject it automatically