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
Usually component files have a schema, determining what data they accept. The mock file can use this schema to provide autocomplete for keys.
The text was updated successfully, but these errors were encountered:
The VS Code YAML extension allows associating schema files (https://github.com/redhat-developer/vscode-yaml#associating-schemas). Unfortunately this doesn’t work when dealing with “dynamic” schema paths.
A solution could be dynamic text documents (microsoft/vscode#127812), but I still don’t know how to associate these with the mocks.yaml files.
mocks.yaml
Another solution could be manually constructing the autocomplete data (https://code.visualstudio.com/api/language-extensions/programmatic-language-features#show-code-completion-proposals).
Sorry, something went wrong.
mvsde
No branches or pull requests
Usually component files have a schema, determining what data they accept. The mock file can use this schema to provide autocomplete for keys.
The text was updated successfully, but these errors were encountered: