This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-05-30
Channels
- # announcements (5)
- # babashka (5)
- # beginners (39)
- # calva (1)
- # chlorine-clover (22)
- # circleci (4)
- # clara (5)
- # clj-kondo (1)
- # cljs-dev (2)
- # cljsrn (8)
- # clojure (46)
- # clojure-canada (15)
- # clojure-norway (3)
- # clojure-uk (6)
- # clojurescript (39)
- # conjure (10)
- # core-async (9)
- # datomic (2)
- # figwheel-main (26)
- # fulcro (33)
- # ghostwheel (9)
- # jobs (6)
- # leiningen (1)
- # malli (7)
- # music (1)
- # off-topic (48)
- # re-frame (11)
- # reagent (1)
- # shadow-cljs (86)
- # spacemacs (8)
It's not stated explicitly to be ordered. But it explicitly requires a sequential collection and it just calls dispatch
in order.
Yea, I didn’t realise that wasn’t part of it’s contract, so it could change order at some point in the future?
The probability is not 0 on the infinite timeline. :P But I really doubt that it will ever happen. Same as with the js/console.log
syntax never going away.
Even if it breaks with some re-frame update, you could just override it with your own version of :dispatch-n
that does everything in the order you desire.
Is there a way to define end to end testing with events in reframe?
Something like running the app and dispatching the events in. Headless browser?
why not simulate the user clicks with something like [cypress](https://github.com/cypress-io/cypress)
Thanks a lot. I will try it. The reason I want to have events is they have better semantics than clicks.