Added a config to directly use top level keys as parameters#55
Open
gido wants to merge 1 commit intoIncenteev:masterfrom
Open
Added a config to directly use top level keys as parameters#55gido wants to merge 1 commit intoIncenteev:masterfrom
gido wants to merge 1 commit intoIncenteev:masterfrom
Conversation
|
+1 This could be helpful for me |
|
that would work for me too 👍 @stof is there any update on this, are there any objections to not merge it or is there maybe another way to do it? |
|
bump. there there any reason to not allow this functionality @stof? |
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
4 participants
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.
My usecase is the following: Some of apps I'm working on are using YAML file to store config without having a single top-level keys (like
parametersorconfig). And I would be happy to be able to use this handy scripts (without the need to change the way we are structuring our config file).I don't know, maybe this is a bit too far away of the original idea of this library...