Make use of jsx compatibe with 3.x #645
Merged
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.
jsx moved to v3.0.0 on Friday, 26 June 2020. See jsx#139. The big change is that the default option is that
return_maps
now defaults totrue
, meaning that you will get maps output unless you explicitly pass[{return_maps, false}]
when decoding JSON.This change updates internal use of jsx to always pass
return_maps
explicitly, true or false, so that it is compatible with jsx v3.0.0. I also updated the pin of jsx to v2.11.0, since I don't want to force 3.x onto clients just yet.