This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-10-16
Channels
- # aws-lambda (10)
- # beginners (52)
- # boot (42)
- # cider (2)
- # cljs-dev (8)
- # cljsjs (4)
- # cljsrn (10)
- # clojars (3)
- # clojure (48)
- # clojure-conj (4)
- # clojure-dev (19)
- # clojure-italy (7)
- # clojure-norway (4)
- # clojure-russia (44)
- # clojure-spec (70)
- # clojure-uk (34)
- # clojurescript (39)
- # cursive (35)
- # data-science (11)
- # datomic (7)
- # emacs (6)
- # fulcro (2)
- # hoplon (12)
- # jobs (1)
- # juxt (18)
- # lein-figwheel (2)
- # leiningen (4)
- # luminus (9)
- # off-topic (29)
- # om (46)
- # onyx (131)
- # other-languages (24)
- # parinfer (84)
- # pedestal (10)
- # portkey (45)
- # protorepl (1)
- # re-frame (15)
- # reagent (43)
- # ring-swagger (41)
- # schema (6)
- # shadow-cljs (293)
- # slack-help (2)
- # specter (42)
@flyboarder i noticed that in your spec you have boolean?
for do!
values, but i think this would mean you cannot trigger an event more than once
e.g. :focus
would have to cycle between true/false and trigger an intermediate focusout
whereas i currently generate a new random value when i want to trigger a focus on certain elements, there's not necessarily a falsey state in between two focuses, it depends on what the user is doing
@thedavidmeister not sure, spec is just to test the value, any time the formula changes value it should fire
Perhaps we need event tests
yeah i think do! does the right thing
i'm suspicious of the spec being too strict in this case
don't have any tests confirming my suspicions though
@flyboarder just taking class for a test spin with some new elements
(def item-wrap (partial h/div :class/item-wrap "item-wrap"))
(def item-core (partial h/div :class/item-core "item-core"))
(def item-details (partial h/div :class/item-details "item-details"))
:thumbsup: no more boilerplate
@thedavidmeister yay!!! I think this will simplify my ui libraries