feat(parser): Support relative paths in references #12
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes kapitan issue #706
Proposed Changes
Keyword reference
To move just one nesting-level back, use
::
, an empty key, e.g.${:::my:key}
To get the name of a key itself, you can use the keyword
.self_name
as an attribute to your current key, e.g.${my:key:.self_name}
Full Example
There shouldn't be any breaking changes!
But if you have any concerns, please let me know.
To Do
${:relative:${absolute}}
works fine${absolute:${:relative}}
doesn't work at the moment. I can't figure out, why the path (the refs location in the dict) sometimes doesn't get passed to the resolving processContributed by