fix: skip redundant computations in the schema subset checker - #110
Merged
l1shen merged 1 commit intoSep 7, 2026
Merged
Conversation
|
Warning Review limit reached
On-demand reviews are free for the next 13 days. After that, they cost $0.25 per reviewed file. Or wait 59 minutes for your next included review. View limit detailsLimit details: You’ve used the included review currently available. Review configuration: ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Team Run ID: 📒 Files selected for processing (2)
Comment |
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
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
Fixes two redundant recomputations in the JSON Schema subset checker: cached falsy results never hit the cache, and
calculateObjectcomputes each optional key expression twice.Changes
checker/cache.ts:getWithCachenow checksresult === undefinedinstead of!result, so cached falsy results (falseandExpressionNone) are reused.checker/equals.tsalready used this form.checker/object.ts: the optional-key loop pushes the already computedexpressioninstead of callingcalculateKeya second time, matching the adjacent additionalProperties block.Motivation
!result, every deep-equality miss (false) and everyExpressionNoneschema comparison bypassed the cache and was recomputed on each lookup.calculateKeytwice per key purely to obtain the same value.Testing
bun run checkandbun run testinpackages/open-flow. Both changes are behavior-preserving; the existing schema-compare suites cover the affected paths.