We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Is there any possibility to let the file specify schema?
When editing the YAML file, the author knows exactly which schema should be applied. So there could be a header or something to specify the schema.
For example:
"http://json-schema.org/schema#": - https://kubernetesjsonschema.dev/v1.14.0/deployment-apps-v1.json - https://kubernetesjsonschema.dev/v1.10.3-standalone/service-v1.json -- apiVersion: v1 kind: Service ......
The example is not ideal. But this VSCode extension could support this non-stranded way. In the future, we can help users immigrate.
Related issue: json-schema-org/json-schema-spec#828 (comment)
The text was updated successfully, but these errors were encountered:
You can reference a JSON Schema inline using: https://github.com/redhat-developer/yaml-language-server#using-inlined-schema
Sorry, something went wrong.
Add 'doDocumentOnTypeFormatting' implementation (redhat-developer#389)
d35e49a
* redhat-developer#179 add 'doDocumentOnTypeFormatting' implementation Signed-off-by: Yevhen Vydolob <[email protected]> * add tests Signed-off-by: Yevhen Vydolob <[email protected]> * add handler Signed-off-by: Yevhen Vydolob <[email protected]> * add missing trigger character Signed-off-by: Yevhen Vydolob <[email protected]> * Update tests Signed-off-by: Yevhen Vydolob <[email protected]>
No branches or pull requests
Is there any possibility to let the file specify schema?
When editing the YAML file, the author knows exactly which schema should be applied. So there could be a header or something to specify the schema.
For example:
The example is not ideal. But this VSCode extension could support this non-stranded way. In the future, we can help users immigrate.
Related issue:
json-schema-org/json-schema-spec#828 (comment)
The text was updated successfully, but these errors were encountered: