Introduce compact keys for JSON metadata fields to reduce size of JSON metadata object #390
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.
High Level Changes
HTTPS://
Why
This PR is meant to address WietseWind's comment in this discussion about reducing the size of JSON metadata object. With the proposed change, we can achieve a ~27.6% size reduction (from ~626 bytes to ~453 bytes) for the JSON Metadata example provided in XLS-89 Multi-Purpose Token Metadata Schema.
Before
JSON Metadata example (626 bytes)
After
JSON Metadata example (453 bytes)