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
When using a set in a spec, the coercion with the json-transformer does not work correctly. Here is a minimal example:
(s/def ::hello #{:one :two :three}) (s/def ::test-set (s/keys :req-un [::hello])) (st/coerce ::test-set (->> {:hello :one} (m/encode "application/json") (m/decode "application/json")) st/json-transformer) ;; => {:hello "one"}
Is it intended to provide the type hint manually as described in the custom coercion section (https://github.com/metosin/spec-tools/blob/master/docs/01_coercion.md)? If so, please close the issue again.
The text was updated successfully, but these errors were encountered:
there is no auto-resolution of set types, you need to have (s/and keyword? #{::one :two :three}) for spec-tools to know the type
(s/and keyword? #{::one :two :three})
Sorry, something went wrong.
No branches or pull requests
When using a set in a spec, the coercion with the json-transformer does not work correctly. Here is a minimal example:
Is it intended to provide the type hint manually as described in the custom coercion section (https://github.com/metosin/spec-tools/blob/master/docs/01_coercion.md)? If so, please close the issue again.
The text was updated successfully, but these errors were encountered: