Serialize additional properties at the end of the json #206
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.
In some cases, the order of the keys is important, it might be for readability or other reasons. With the current implementation, every additional property is added at the beginning of the json, making it very hard to guarantee the order of the keys if you don't know them in advance.
This pr fixes this and serialize additional/pattern properties at the end of a json string.
Not sure if we should consider this a breaking change, as usually people test their code with
JSON.parse
.Checklist
npm run test
andnpm run benchmark