This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-03-25
Channels
- # aws (1)
- # beginners (60)
- # boot (12)
- # cider (7)
- # cljs-dev (8)
- # cljsrn (24)
- # clojure (169)
- # clojure-nl (1)
- # clojure-russia (3)
- # clojure-spec (15)
- # clojure-switzerland (1)
- # clojure-uk (24)
- # clojurescript (120)
- # core-async (9)
- # datomic (3)
- # emacs (2)
- # gsoc (3)
- # klipse (2)
- # leiningen (4)
- # numerical-computing (13)
- # off-topic (95)
- # om (7)
- # onyx (1)
- # powderkeg (2)
- # protorepl (2)
- # re-frame (6)
- # reagent (58)
- # ring-swagger (1)
- # rum (28)
- # untangled (42)
- # vim (6)
I'm actually a bit confused about link queries. Do they allow me to have 'floating' queries that do not compose up to root through the parent components? If I have to hike them up through the tree into each parent, it's still a bit inconvenient. I might as well pass user down the tree...
@danielstockton idents can "float" outside the hierarchy
That's indeed very useful then, I will give that a go.
I also had trouble rooting a nested remote query, sadly I never worked it out and can't use an ident in that case.
What I wanted was a component two levels deep to have a root query and to use a namespaced keyword on the parent and grandparent just for passing props down. I tried calling it :delegate/some-name
meaning it delegates the query to the next level and checked for the delegate
namespace in the :default
parser function. I got it to work with local queries but if I added :remote true
it sent the whole thing and I never worked out how to root it. Tried associng :query-root true
in various places to no avail.
If anyone is doing something similar in their project or knows an example, I'd be interested to hear.