Add doc references and add examples for <> values

[EmilyGraceSeville7cf]

• bashly
• settings
• strings
• examples for completions property

Notes

Regex used to speed up adding doc references:

• from: "title": "(.*)",\n(\s+)"description": "(.*)",
• to: "title": "$1",\n$2"description": "$3\\nURL/#$1",

[DannyBen]

Do you prefer that I merge #399 so you have my latest schema?

[EmilyGraceSeville7cf]

Do you prefer that I merge #399 so you have my latest schema?

@DannyBen, yes, please.

[DannyBen]

Merged. Change as you wish.

[DannyBen]

is there any list of all possible special values for completions property like <user>?

Yes.
https://github.com/DannyBen/completely#suggesting-files-directories-and-other-bash-built-ins

But - notice that there may be other possibilities that are not listed, since these types of strings are simply used differently. From the completely page (appears below that list):

For those interested in the technical details, any word between <...> will simply be added using the compgen -A action function, so you can in fact use any of its supported arguments.

So - if there is a way to suggest this list, but still allow any other <...> option - it is okay.

Let me know if wait or merge.

[EmilyGraceSeville7cf]

You can merge.

[DannyBen]

Nice. Thanks for this.

I wonder why JSON schema doesn't have a dedicated field for reference/documentation. Seems basic.

[EmilyGraceSeville7cf]

I wonder why JSON schema doesn't have a dedicated field for reference/documentation. Seems basic.

The same question. I think they can introduce something like documentation property for this purpose, but it will be useless for VS Code users until any extension supports it. As the goal it to show doc URL in key description and not to force user to open JSON schema and dig into it to just find out the right link for the documentation.