fix: skip JSON Schema combinators in sealSchemaDeep and unsealSchemaDeep
#85
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
🦋 Changeset detectedLatest commit: c38dde9 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
Pull Request Test Coverage Report for Build 18915039245Details
💛 - Coveralls |
toomuchdesign
force-pushed
the
fix-sealSchemaDeep-array-types
branch
from
e412e85 to
ea0f7d4
Compare
toomuchdesign
changed the title
toomuchdesign
changed the title
sealSchemaDeep and unsealSchemaDeep
toomuchdesign
added a commit
that referenced
this pull request
Oct 30, 2025
This PR was opened by the [Changesets release](https://github.com/changesets/action) GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to master, this PR will be updated. # Releases ## @toomuchdesign/json-schema-fns@0.6.1 ### Patch Changes - [#85](#85) [`452602c`](452602c) Thanks [@toomuchdesign](https://github.com/toomuchdesign)! - `unsealSchemaDeep`: do not modify `allOf`, `anyOf`, `oneOf`, or `not` values - [#85](#85) [`452602c`](452602c) Thanks [@toomuchdesign](https://github.com/toomuchdesign)! - `sealSchemaDeep`: do not modify `allOf`, `anyOf`, `oneOf`, or `not` values Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
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.
What kind of change does this PR introduce?
Bug fix
What is the current behaviour?
sealSchemaDeepandsealSchemaDeepchange the logical meaning of JSON Schema combinators such asallOf,anyOf,oneOf, ornot.What is the new behaviour?
Skip
allOf,anyOf,oneOf, ornotvaluesDoes this PR introduce a breaking change?
No
Other information:
Please check if the PR fulfills these requirements: