This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-04-20
Channels
- # announcements (1)
- # asami (6)
- # babashka (21)
- # beginners (19)
- # calva (44)
- # circleci (3)
- # clj-http (3)
- # clj-kondo (44)
- # clojure (24)
- # clojure-australia (1)
- # clojure-czech (1)
- # clojure-europe (50)
- # clojure-france (5)
- # clojure-germany (1)
- # clojure-nl (2)
- # clojure-spec (8)
- # clojure-uk (8)
- # clojurescript (161)
- # datomic (4)
- # fulcro (7)
- # graalvm (8)
- # heroku (4)
- # lambdaisland (4)
- # lein-figwheel (5)
- # lsp (48)
- # malli (21)
- # meander (15)
- # off-topic (35)
- # polylith (2)
- # re-frame (21)
- # react (22)
- # reagent (13)
- # reitit (6)
- # remote-jobs (1)
- # reveal (3)
- # ring (3)
- # shadow-cljs (37)
- # testing (2)
- # tools-deps (10)
- # vim (18)
- # vrac (1)
- # xtdb (17)
Hmm, seems like df/load!
does not support loading a list of idents in one transaction... do we need to implement that ourselves?
what do you mean? df/load
uses a component's query, and the ident is just where that query is rooted, and a query can't have more than one root, so it can't have more than one ident. You can use targeting to merge query result to other places in your state if that's what you're trying to do
Basically, I would like to have multiple df/load!
s merged into one transaction, using the default actions that come with df/load!
.
tony was recently working on having just that happen automatically, actually https://github.com/fulcrologic/fulcro/commit/35a47b26f366833de26b496a1902b5232dba1431
Also, why do you need that? Perhaps there is another solution? If you were loading Persons, you could have a resolver for all-people, perhaps parameterized to limit which ones to return.
@U0522TWDA Because this list is determined by the client. For example, it is based on a box selection in the UI.
I see. Still, you could make a parametrized resolver that takes a list of IDs and use that. No?