fix: allow camel-cased json components to be used in payloads #7392
Conversation
This file contains 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
suneettipirneni
changed the title
imranbarbhuiya
suggested changes
Feb 2, 2022
Co-authored-by: Parbez <[email protected]>
kyranet
requested changes
Feb 2, 2022
Co-authored-by: Antonio Román <[email protected]>
suneettipirneni
force-pushed
the
feat/decamelizer
branch
from
ac7ba91
to
5e75105
Compare
|
I don't understand why this can't be left to the user to handle? |
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.
Please describe the changes this PR makes and why it should be merged:
This fixes a regression where sending in camelCased json objects in message payloads wouldn't work.
Closes #7376
Depends on:
xURLtoxUrl#7388Status and versioning classification: