Fix serializer bug regarding capped repeated fields that aren't at the end #525
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
…e end If, like in `HIUPDv6`, a repeated field is followed by another field, then we need to ensure that the next field writes its content to the correct `$index` (namely behind the space occupied by the repeated field) instead of overwriting the values of the repeated field. See nemiah#521
Contributor
|
Awesome! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
If, like in
HIUPDv6, a repeated field is followed by another field, then we need to ensure that the next field writes its content to the correct$index(namely behind the space occupied by the repeated field) instead of overwriting the values of the repeated field.Fixes #521