Merge with primary schema #4
Open
Conversation
This file contains 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
…ey are merged into the primary.
|
I'd love to see that PR merged! :) |
|
Yes, this looks like a good feature to have! |
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.
Added the optional ability to mark schemas for merging. Any marked schema is merged into the default_map, just as the primary schema is. I also added a note about this to the docs and added a test.
Example usage can be seen in the tests. In short, this uses another list in
ConfigFileReadercalledconfig_section_primary_schemas, similar toconfig_section_schemas.Default behavior is unchanged.
This is a solution to #2