🐛 fix: merging of two similarly keyed mappings#11
Merged
RobertoPrevato merged 1 commit intoNeoteroi:mainfrom Dec 28, 2023
Merged
🐛 fix: merging of two similarly keyed mappings#11RobertoPrevato merged 1 commit intoNeoteroi:mainfrom
RobertoPrevato merged 1 commit intoNeoteroi:mainfrom
Conversation
Member
|
Hi @StummeJ |
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
2 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.
Overview
This sets out to fix issue #10. We found that merging two sources with similar mappings would cause the destruction of the mapping from the previously processed source. The use case we found this in was having a config with some secret values, then populating just the secret values from a secure store.
Specifics
deepmergepackage to handle merging of two mappings properlyTEST_environment variables for it's test runner