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
If I set up a params object (naming it validate-account to not shadow the params function, which I think is a bad example)
validate-account
(def validate-account (params :accounts (validates [:name :real-name] :required true) (permit [:name :real-name])))
The documented behavior is not met, in fact both the error case and the successful case do not work as described.
repl:39:> (rescue (validate-account {:name "hello"})) (@{:name "name is required" :real-name "real-name is required"} nil) repl:40:> (rescue (validate-account {:name "hello" :real-name "real"})) (@{:name "name is required" :real-name "real-name is required"} nil)
Instead the true behavior is found when it is wrapped in {:body {...}}
{:body {...}}
repl:41:> (rescue (validate-account {:body {:name "hello"}})) (@{:real-name "real-name is required"} nil) repl:42:> (rescue (validate-account {:body {:name "hello" :real-name "real"}})) (nil @{:db/table :accounts :name "hello" :real-name "real"})
The text was updated successfully, but these errors were encountered:
Hmm maybe there should be a validate-body and validate for requests and for regular dictionaries
Sorry, something went wrong.
No branches or pull requests
If I set up a params object (naming it
validate-account
to not shadow the params function, which I think is a bad example)The documented behavior is not met, in fact both the error case and the successful case do not work as described.
Instead the true behavior is found when it is wrapped in
{:body {...}}
The text was updated successfully, but these errors were encountered: