This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-08-21
Channels
- # aleph (2)
- # beginners (22)
- # boot (7)
- # chestnut (8)
- # cider (4)
- # clara (3)
- # cljs-dev (3)
- # cljs-experience (19)
- # clojure (69)
- # clojure-italy (8)
- # clojure-nl (1)
- # clojure-spec (11)
- # clojure-uk (17)
- # clojurescript (77)
- # cursive (22)
- # datomic (14)
- # events (1)
- # fulcro (78)
- # hoplon (51)
- # jobs (3)
- # keechma (1)
- # lambdaisland (1)
- # lumo (30)
- # off-topic (42)
- # om (22)
- # onyx (5)
- # parinfer (4)
- # portkey (1)
- # re-frame (15)
- # reagent (2)
- # ring (4)
- # spacemacs (1)
- # specter (23)
- # testing (1)
- # unrepl (60)
- # yada (8)
I'm using Yada for a traditional server-side rendered app. What is the recommendation for doing form validations? Yada throws an error if the POST parameters are incorrect, which makes sense for an API, but is not the friendliest for a user facing form.
@danielcompton you can control the contents of a response for a 400 error 🙂 So you can take the message and do what you want with it (e.g. run it through vlad)
Is a 400 status useful for a well-formed request entity with invalid data, especially for a browser POST?
Haven't checked the source, but there's a chance that the validation is replaceable/extendable in some way (likely with a new interceptor), so you could do something in that way
Was chatting with malcolm the other day about potential futures of the validation api
Thanks 🙂
Great, will start with that first