the to-validator
function in the forms example seems to be generic and helpful enough that it could probably be included in the forms library?
it is something that I see myself having to copy/paste for every new project
it’s not really generalized and there might be better ways to write it. it depends how you would want to format the validations map. But I agree that a generalized solution might make sense
also I’m not sure If you’ve seen this, but Keechma Forms allows the best validation UX 🙂 https://medium.com/wdstack/inline-validation-in-forms-designing-the-experience-123fb34088ce#.mdeu0s4br
hadn’t seen it 🙂
Hadn't read it. That's why I picked keechma to start learning, though. I'm trying to introduce validations on a wonky set of data in an HR context
I'd love to something like this work out for the poor folks that do data entry. http://blog.cognitect.com/blog/2015/5/14/breeze-ehr-to-simplify-healthcare-with-clojure-and-datomic
Life lesson "Hybrid — reward early, punish late — approach"
(defrecord Controller [main-app]
controller/IController
(params [_ route-params] true)
(handler [this app-db-atom in-chan _]
(let [main-app (:main-app this)
user (cks/get :current-user)]
(if user
(start-app! main-app app-db-atom)
(controller/dispatcher app-db-atom in-chan
{:login (partial login main-app)})))))
vs
(go (start-app! main-app app-db-atom)
So everything delegated from a controller must be async. Is this correct? Understandable style?