Setting the $schema property

[Tony Peguero (Plasmadog)]

Is there a way to have the generated spec include a $schema property? It's annoying to have Visual Studio complaining about schema validation issues.

[Vincent Biret (baywet)]

Hi Tony Peguero (@Plasmadog)
Thank you for using the SDK and for reaching out.

You shouldn't be setting $schema at the root of the document, but rather:

• setting jsonSchemaDialect if you mean to use a different dialect for all schema obejcts
• setting the $schema keyword on a per schema basis
• using the tooling in Visual Studio or equivalent to select which schema to use to validate the structural integrity of the document.

On that later point, we've made ecosystem improvements:

• multiple fixes for OpenAPI schemas at the schema store level this should allow Visual Studio to correctly select the appropriate schema to apply to your document
• support for JSON schema 2020 for the language server, so Visual Studio understands the new semantics of those schema when performing the validation
• support for schema store in VSCode so that VSCode can also pull schemas from schema store, this one is not merged yet, please upvote it if you think you'd need it. Visual Studio already has an integration with schema store as far as I understand.
  Let me know if you have any additional comments or questions.