Pass current field name to raw BSON decoder #326
Closed
Conversation
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
|
Thanks again for your contributions. As mentioned in #324, I think using raw documents for this use case is the wrong thing to do. |
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.
This PR makes both python and c BSON decoder implementation pass current decoding field name to raw BSON decoder (e.g. RawBSONDocument). It is needed to add some name-dependent decoding behaviour.
In addition to context sharing between decoding levels from #324 it can give custom BSON decoder such feature like decoding map (e.g.
fooarray would be decoded toFooClassobject, and the innerfoo.bararray would be wrapped byBarClass)