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
We should be able to both declare and derive/infer effective types for wrapper schemas like :and, :multi and :enum.
:and
:multi
:enum
forked from #246. Replaces #39.
:map
[:multi {:dispatch :type} [:sized [:map [:type [:= :sized]] [:size int?]]] [:human [:map [:type [:= :human]] [:name string?] [:address [:map [:country keyword?]]]]]]
:int
[:fn {:type :int} '(fn [x] (< 10 x 100))]
:keyword
[:enum :kikka :kakka :kukka]
[:and keyword? keyword?]
[:or keyword? [:fn {:type :keyword} '(fn [x] (keyword? x)]]
The text was updated successfully, but these errors were encountered:
:type
working on this.
Sorry, something went wrong.
Hi. Just wondering, in #782 (which is closed and refers to this issue) support was added for:
(m/decode [:enum :A :B :C] "A" (mt/string-transformer)) ;; => :A
Is this "full solution" going to include support for going the other way? i.e.:
(m/encode [:enum :A :B :C] :A (mt/string-transformer)) ;; => "A"
or should I open a separate issue (or is there a reason it perhaps isn't going to be done)?
Cheers
ikitommi
No branches or pull requests
We should be able to both declare and derive/infer effective types for wrapper schemas like
:and
,:multi
and:enum
.forked from #246. Replaces #39.
This is clearly also a
:map
this is an
:int
and this is a
:keyword
this too
[:and keyword? keyword?]
and this
The text was updated successfully, but these errors were encountered: