Open
Conversation
Before this commit, only keys mentionned in the `Mapper` through the `map` method were treated. Other input keys were ignored. Now you can pass the option `keep_unmapped_keys` to the `normalize` method to let unmapped keys go from input to output without being touched.
romaind
force-pushed
the
allow-keeping-unmapped-keys
branch
from
87a5923 to
9e48455
Compare
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
1 participant
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.
In my use case, I wanted to map some keys but keep others as is and did not want to have to map them with themselves all the time.
So I created a new option that tells the lib to keep unmapped key as is and return them in the output just as they were in the input.
Maybe it could be useful for others