This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-08-03
Channels
- # bangalore-clj (1)
- # beginners (104)
- # boot (30)
- # braveandtrue (1)
- # cider (6)
- # cljs-dev (95)
- # cljsjs (16)
- # cljsrn (3)
- # clojure (106)
- # clojure-italy (15)
- # clojure-nl (2)
- # clojure-norway (3)
- # clojure-russia (1)
- # clojure-spec (40)
- # clojure-uk (53)
- # clojure-ukraine (1)
- # clojurescript (200)
- # code-reviews (2)
- # cursive (1)
- # datascript (3)
- # datomic (32)
- # editors (28)
- # gorilla (6)
- # graphql (8)
- # hoplon (1)
- # jobs (8)
- # jobs-discuss (5)
- # jobs-rus (1)
- # keechma (13)
- # leiningen (5)
- # luminus (3)
- # lumo (53)
- # off-topic (5)
- # om (5)
- # om-next (1)
- # onyx (56)
- # parinfer (7)
- # protorepl (22)
- # re-frame (47)
- # reagent (37)
- # remote-jobs (1)
- # ring-swagger (9)
- # specter (7)
- # vim (14)
- # yada (30)
@pupeno question for you about FreeForm. When you toggle a checkbox the event is updated with the value, i.e. you can't distinguish between checking & unchecking. In general of course this shouldn't be a problem since there should be no way for the form and your "in db" model to get out of sync although in testing i've managed to do this a couple of times (possibly related to Chrome's reloading issues)
@pupeno the question is, is it intentional? Or would it be better for a checkbox to send .-checked
instead of .-value
?
Interesting. Let me see.
Ah... right... I haven't even worked on checkboxes yet.
at the moment i am just using the event as a trigger for update not
which is fine but makes me uncomfortable
I think the checkbox should generate it's current state and not the toggle.
That's in-sync with the rest of the functionality anyway.
So, no, it's not intentional and I'd tend to agree with you (without looking too much into it).
probably a relatively simple patch to bind-input
i could have a crack at it if you like, but happy to leave to you if you'd prefer
I'm happy for you to work on it, give me a couple of hours to clean up free-from (it was in the middle of a refactor that should be abandoned).
I will work a lot on Free form once I release my startup product, so, in the next couple of months, but not sure when.
Is it bothering you in some way? The reason it's there is so that Cursive users will get code style, testing profiles, etc without having to do any work.
It is deliberate but not battle tested. If it's annoying other people, not working, etc, then I'll remove it.
Hrmm... Error synchronising com.pupeno/free-form:0.6.0-SNAPSHOT: Could not find artifact tech.dashman:reagent-toolbox:jar:0.1.0-SNAPSHOT in clojars (https://clojars.org/repo/)
Yes... that's the issue.
I'm starving, but give me a sec to try to fix it.
Try again.
I mean, do a git pull.
I think someone else did it, but it wasn't released.
We should add the checkbox and radio buttons to the examples.
I'll grab some food and look into this. It might be time for a release.
I'm back.
@sandbags I try to keep the changelog complete.
It's at the bottom of the readme.
Ah... we do have checkbox and radio buttons in the example, I just never pushed it.
I'm going to do a 0.6.0 release with that.
@sandbags checkboxes and radio buttons: http://free-form-examples.pupeno.com/reagent/bootstrap-3