This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-06-17
Channels
- # admin-announcements (4)
- # boot (93)
- # cider (4)
- # cljsrn (61)
- # clojure (137)
- # clojure-austin (2)
- # clojure-brasil (2)
- # clojure-dev (11)
- # clojure-dusseldorf (10)
- # clojure-greece (245)
- # clojure-russia (37)
- # clojure-spec (60)
- # clojure-taiwan (1)
- # clojure-uk (24)
- # clojurescript (36)
- # cursive (18)
- # datomic (20)
- # emacs (20)
- # funcool (1)
- # hoplon (29)
- # jobs (1)
- # keechma (1)
- # lein-figwheel (1)
- # leiningen (1)
- # off-topic (3)
- # om (10)
- # om-next (1)
- # onyx (60)
- # other-languages (14)
- # planck (26)
- # random (3)
- # re-frame (21)
- # ring (2)
- # spacemacs (8)
- # specter (56)
- # spirituality-ethics (2)
- # uncomplicate (1)
- # untangled (68)
- # yada (3)
@nxqd: @iwankaramazow: the problem in your example is that you’re setting both the Root query and the Wrapper query
whenever you get the query for the Root, since you set it dinamically, whatever has been set for it is going to win
in this case you have set it when the id
param was still nil
@anmonteiro: thanks ! it explains the problem.
im having trouble querying for a many enum attribute.
i.e. [:db/id :foo/bar {:foo/zed [:db/ident]}]
is there a proper way to query for many enum that i am missing? on the server this query looks the same and returns the actual values
looks like a known issue: https://github.com/omcljs/om/issues/604
@anmonteiro: thanks! Om Next's fundamentals are so important 😄
I've run into the #error {:message "No queries exist for component path [...]
a few times and it seems to have something to do with the query in my root component and (possibly) the metadata from get-query
calls inside the root query.
A simplified example:
Header query:
[:app/name]
Counter query:
[:app/count]
Root query:
`[~@(om/get-query Header)
~@(om/get-query Counter)])
Setup this way, the child components get the right props, but calls to transact!
from the child components throw the "No queries" error.
Does someone know if this is expected behavior?
EDIT: adjusted typos in query names