You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your enhancement related to a problem? Please describe.
I am frustrated when I am referencing a file in a yaml and I cannot verify if the path is correct by cmd+click-ing on the path to be taken to target. Further in complex k8s deployments it would be useful to be able to jump between nested folders using the defined kustomize resources.
Describe the solution you would like
If I define a string value as file:// vscode correctly references and links to the target resource. I would expect that when a Schema is known, vscode-yaml would also link a path, even without the file:// URI-prefix.
Describe alternatives you have considered
I have explored explicitely defining a file:// prefix, however this is not compatible with k8s kustomize and would add a large overhead to every file.
I can confirm that this is an issue with .gitlab-ci.yml files as well, even though the values in the schema are defined with format: uri-reference (link) and some of the files being referenced are available locally, I'm not able to cmd + click (on macos) to navigate to those files at all within VS Code + vscode-yaml.
bleach31
pushed a commit
to bleach31/vscode-yaml
that referenced
this issue
Jan 25, 2022
Is your enhancement related to a problem? Please describe.
I am frustrated when I am referencing a file in a yaml and I cannot verify if the path is correct by cmd+click-ing on the path to be taken to target. Further in complex k8s deployments it would be useful to be able to jump between nested folders using the defined kustomize resources.
Describe the solution you would like
If I define a string value as
file://
vscode correctly references and links to the target resource. I would expect that when a Schema is known, vscode-yaml would also link a path, even without thefile://
URI-prefix.Describe alternatives you have considered
I have explored explicitely defining a
file://
prefix, however this is not compatible with k8s kustomize and would add a large overhead to every file.Additional context
https://github.com/kubernetes/kubectl/blob/master/docs/book/pages/reference/kustomize.md#resources
The text was updated successfully, but these errors were encountered: