This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-06-16
Channels
- # arachne (1)
- # beginners (27)
- # boot (17)
- # cider (10)
- # cljs-dev (5)
- # cljsrn (76)
- # clojure (59)
- # clojure-austin (2)
- # clojure-brasil (1)
- # clojure-greece (76)
- # clojure-mexico (1)
- # clojure-quebec (63)
- # clojure-russia (16)
- # clojure-spec (127)
- # clojure-uk (12)
- # clojurescript (72)
- # community-development (7)
- # core-async (3)
- # core-matrix (2)
- # cursive (13)
- # datomic (8)
- # emacs (4)
- # funcool (4)
- # hoplon (148)
- # immutant (5)
- # keechma (2)
- # lambdaisland (5)
- # lein-figwheel (15)
- # leiningen (20)
- # off-topic (23)
- # om (13)
- # om-next (19)
- # onyx (11)
- # planck (11)
- # re-frame (59)
- # reagent (14)
- # rum (34)
- # specter (30)
- # spirituality-ethics (16)
- # uncomplicate (5)
- # untangled (387)
- # yada (2)
@petterik: right, that problem shouldn't happen with unions. You'll probably get into others which will seem to suggest you should re-root queries, but I wouldn't fall for that!
I have yet to find a scenario where process-roots
is useful
So far just leveraging the AST has been more than enough, and much more flexible too
@anmonteiro: Can you explain (or point to an example) where leveraging the AST is used to manipulate the query such that a remote read is handled as a "query-root" alike but the results are merged deep into the client state?
I'm thinking of a scenario like loading additional (remote) details for some nested item on demand.
@anmonteiro: can you help me out with this ? I think it's a good idea that the params of component-path->query
should be kept in sync with the individual component as well.
If you might have a different approach to this problem, I would love to know. Thanks in advanced.
@anmonteiro: have you had any time to think about our discussion about having something in om like datomic’s db-before
and db-after
?
ran into another scenario this morning where it would have been handy
Does ComponentDidMount not provide previous state and current state parameters? Im sure tough its not the same.
@cmcfarlen: that doesn’t seem troubling to me if you’re using normalization
after all normalized data is not deep in the app-state, but at the top level
I suppose you’d need to have some custom logic in merge
or send