feat: flexible matcher architecture and null/empty array equivalence #20
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.
Summary
This PR introduces a more flexible matcher architecture and adds the ability to treat
nulland empty arrays[]as equivalent.Closes #17
Breaking Changes
CompositeJsonMatcher API
The constructor now accepts varargs instead of 3 fixed parameters:
PartialJsonMatcher interface
New method
manage(JsonNode expected, JsonNode received)required to determine if a matcher handles a comparison.LenientNumberPrimitivePartialMatcher
No longer uses delegation pattern. Must be used alongside
StrictPrimitivePartialMatcher:New Features
NullEqualsEmptyArrayMatcher
Treats
nulland[]as equivalent:Note: Missing properties do NOT match empty arrays (intentional design decision).
Changes
manage()methodmanage()method to interfaceTest Plan
NullEqualsEmptyArrayMatcherLenientNumberPrimitivePartialMatcherrefactoringCompositeJsonMatcherTestfor new API🤖 Generated with Claude Code