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
Use case Working on a large project, with lots of CRDs in lots of YAML definition files in a deeply-nested build output directory.
Feature The existing crdSchemaLocations would have support for globs, and visual-studio-code settings built-ins like ${workspaceFolder}.
crdSchemaLocations
${workspaceFolder}
e.g.
"cloudcode.yaml.crdSchemaLocations": [ "${workspaceFolder}/bazel-output/crds/**/*.yaml" ]
Which would match files:
bazel-output/crds/myThing/definition.yaml
bazel-output/crds/otherThing/nestedDeeper/definition.yaml
Ideally, this would also be tolerant of YAML files that match the glob and are not CRDs too (and would just ignore them).
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Use case
Working on a large project, with lots of CRDs in lots of YAML definition files in a deeply-nested build output directory.
Feature
The existing
crdSchemaLocations
would have support for globs, and visual-studio-code settings built-ins like${workspaceFolder}
.e.g.
Which would match files:
bazel-output/crds/myThing/definition.yaml
bazel-output/crds/otherThing/nestedDeeper/definition.yaml
etc.
Ideally, this would also be tolerant of YAML files that match the glob and are not CRDs too (and would just ignore them).
The text was updated successfully, but these errors were encountered: