Fix post processor breaking large fields in multiple parts. #337
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
1 task
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.
Identify the Bug
The post processor was breaking up large post fields into multiple values as if provided separately.
Description of the Change
Now the post processor checks for the offset value. If there is an offset, the value must be a part of a large post field and not an independent repeated value. In this case, we just append to the latest value for the specified argument.
Alternate Designs
None
Possible Drawbacks
None
Verification Process
Added new integration tests.
Release Notes
Fixed the post processor that was breaking up large post fields into multiple values as if provided separately.