This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-12-01
Channels
- # adventofcode (11)
- # aws (8)
- # beginners (70)
- # boot (2)
- # cider (9)
- # cljs-dev (29)
- # cljsrn (2)
- # clojure (67)
- # clojure-android (2)
- # clojure-dusseldorf (5)
- # clojure-greece (12)
- # clojure-italy (4)
- # clojure-nl (3)
- # clojure-poland (3)
- # clojure-russia (5)
- # clojure-spec (80)
- # clojure-uk (9)
- # clojurescript (73)
- # core-async (17)
- # cursive (1)
- # data-science (5)
- # datomic (29)
- # emacs (5)
- # fulcro (257)
- # graphql (2)
- # hoplon (2)
- # jobs (2)
- # klipse (3)
- # leiningen (9)
- # lumo (4)
- # nyc (1)
- # off-topic (48)
- # om (7)
- # other-languages (11)
- # pedestal (4)
- # re-frame (18)
- # remote-jobs (1)
- # rum (10)
- # shadow-cljs (5)
- # spacemacs (20)
- # sql (5)
- # test-check (44)
- # unrepl (8)
- # yada (9)
@daniel.dyba I recommend you to try #fulcro, it makes the development in Om.next much much easier, working from om.next raw is kind insane if you just trying to get an app out
Did anybody encounter the error "No queries exist for component path"? What does it mean? To me it occurs when I do a mutation.
@roti about the mutatoin, you probably forgor to put your function on :action
on the output
om.next calls the mutations once for the local, and one more for each remote (usually 1)
so you can't put the code strait on the mutation, you have to put on a :action key returned by it
eg: (defmethod mutate 'do-something [_ _ _] {:action (fn [] DO_THINGS_HERE)})