redhat-developer / redhat-developer/vscode-yaml

Detect file paths and correctly link/reference target

Open
#559 2 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
TypeScript
Stars
829
Forks
260
Avg merge
5h 43m
Merged PRs (30d)
1

Description

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.

Additional context

image

https://github.com/kubernetes/kubectl/blob/master/docs/book/pages/reference/kustomize.md#resources

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the linked Kubernetes kustomize resources documentation and compare its path forms with VS Code's existing file:// linking behavior. Trace how known schemas and YAML string values are handled, then add coverage for resolving a schema-defined path and verify that cmd-click reaches nested kustomize resources without the URI prefix.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript, vscode
Domain
developer-experience, tooling
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.