feat(base-json): new JSON module with typed value model, reader/writer, and JSONTestSuite compliance#54
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Introduces
base-json, a new JPMS module providing a typed, immutable JSON value model —JsonValueas a sealed interface permittingJsonObject,JsonArray,JsonString,JsonNumber,JsonBoolean, andJsonNull. Includes a hand-written recursive-descentJsonReader(backed bybase-parsing'sAbstractParser/Ruleframework), aJsonWriterwith compact and pretty-print formatting, and fluent builder APIs for objects and arrays.JsonObjectpreserves insertion order throughout — parsed objects,JsonObject.of(map), and the builder all useLinkedHashMapas the backing store, so key iteration order matches document order and round-trips are stable.The
JsonReaderis validated against the full JSONTestSuite corpus: ally_(must accept) andn_(must reject) cases are enforced;i_(implementation-defined) cases are accepted either way. Parse errors carry line, column, byte offset, and a JSON-pointer-style path to the failing value.Inspired by https://openjdk.org/jeps/8344154.