1ca691de09
## Description > Now JSON is rendered in ordered format - When JSON used to be parsed, the order of the keys were randomly/alphabetically ordered. some users needed these to be unmodified for sending checksum as headers, the previous fix for issue #23456 only dealt with first order trees. In this Pr we have used the Gson to parse the JSONs. GSON natively used linkedHashMaps for their JSONObjects, which preserves their keys order. One downside for this is that GSON is a strict parser which parses json only according to RFC4627. - If GSON fails to parse the json (may happen because of invalid json) we will fallback to older parsing strategy which is lenient in parsing JSONs. #### PR fixes following issue(s) Fixes #23456 #### How Has This Been Tested? - [x] Manual - [x] JUnit <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit ## Summary by CodeRabbit - **New Features** - Enhanced JSON parsing to ensure the order of keys is preserved, improving data consistency. - Introduced support for new data types in the API plugin. - **Refactor** - Updated JSON handling logic for better performance and reliability. - **Tests** - Modified tests to align with the updated JSON parsing and header order. <!-- end of auto-generated comment: release notes by coderabbit.ai --> |
||
|---|---|---|
| .. | ||
| src | ||
| pom.xml | ||