We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
:merge
If schemas with registries are merged with :merge, the dereferenced schema often cannot be round-tripped.
Notice the following schema is missing a ::z binding so is no longer well-formed.
::z
(-> (m/deref [:merge [:map {:registry {::y int?}} [:y ::y]] [:map {:registry {::z boolean?}} [:z ::z]]] options) m/form) => [:map {:registry {::y boolean?}} [:y ::y] [:z ::z]]
We might be able to fix this by merging the registries, but something else is needed if the registries both define the same names.
For example, here the schema for :y is being captured by the wrong scope, and becomes [:y boolean?] instead of [:y int?].
:y
[:y boolean?]
[:y int?]
(-> (m/deref [:merge [:map {:registry {::y int?}} [:y ::y]] [:map {:registry {::y boolean?}} [:z ::y]]] options) m/form) => [:map {:registry {::y boolean?}} [:y ::y] [:z ::y]]
The text was updated successfully, but these errors were encountered:
This example doesn't work at all, and complains that ::y is not in scope.
::y
[:merge [:map {::y boolean?} [:y ::y]] [:map]]
Sorry, something went wrong.
No branches or pull requests
If schemas with registries are merged with
:merge
, the dereferenced schema often cannot be round-tripped.Notice the following schema is missing a
::z
binding so is no longer well-formed.We might be able to fix this by merging the registries, but something else is needed if the registries both define the same names.
For example, here the schema for
:y
is being captured by the wrong scope, and becomes[:y boolean?]
instead of[:y int?]
.The text was updated successfully, but these errors were encountered: