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
This is similar to Issue 178 (Fixed by PR 219, but for a specific case.
I'm not sure if this is intended, but it was surprising to me.
Consider the following case where we want to allow something like either {:a 1} or {:b "foo"}
{:a 1}
{:b "foo"}
(s/def ::a int?) (s/def ::b string?) (s/def ::c (s/or :a (s/keys :req-un [::a]) :b (s/keys :req-un [::b]))) ((s/valid? ::c {:a 1}) ; => true (st/coerce ::c {:a 1} st/strip-extra-keys-transformer) ; => {}
However, If i change ::c to:
::c
(s/def ::c (s/or :a (st/spec (s/keys :req-un [::a])) :b (st/spec (s/keys :req-un [::b]))))
NOTE: the st/spec s
st/spec
Now we get:
(s/valid? ::c {:a 1}) ; => true (st/coerce ::c {:a 1} st/strip-extra-keys-transformer) ; => {:a 1}
My expectation is either of these two should be able to be coerced, is that correct?
The text was updated successfully, but these errors were encountered:
No branches or pull requests
This is similar to Issue 178 (Fixed by PR 219, but for a specific case.
I'm not sure if this is intended, but it was surprising to me.
Consider the following case where we want to allow something like either
{:a 1}
or{:b "foo"}
However, If i change
::c
to:NOTE: the
st/spec
sNow we get:
My expectation is either of these two should be able to be coerced, is that correct?
The text was updated successfully, but these errors were encountered: