feat(parser): Support relative paths in references#12
Draft
MatteoVoges wants to merge 3 commits intokapicorp:developfrom
Draft
feat(parser): Support relative paths in references#12MatteoVoges wants to merge 3 commits intokapicorp:developfrom
MatteoVoges wants to merge 3 commits intokapicorp:developfrom
Conversation
This allows us to specify relative paths and use some predefined keyword-functions
The keyword '.self_name' was missing its access operator
Handle Indexerror when calling '.self_name' out of range
|
@MatteoVoges. This is really great. I like the I don't get the use case for |
Author
You're right. I completely missed that. I have chosen the symbols as in unix and developed it first without thinking of some usecases. I will remove it soon! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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_nameas 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