This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-01-31
Channels
- # announcements (4)
- # babashka (73)
- # beginners (128)
- # bristol-clojurians (1)
- # calva (8)
- # cider (8)
- # clj-kondo (4)
- # clojars (7)
- # clojure (148)
- # clojure-dev (16)
- # clojure-europe (5)
- # clojure-gamedev (1)
- # clojure-italy (10)
- # clojure-nl (7)
- # clojure-uk (57)
- # clojurescript (57)
- # clojutre (1)
- # community-development (2)
- # cursive (7)
- # data-science (1)
- # datascript (5)
- # datomic (9)
- # events (6)
- # figwheel-main (1)
- # fulcro (91)
- # garden (11)
- # graalvm (14)
- # graphql (1)
- # immutant (4)
- # jobs (1)
- # kaocha (33)
- # off-topic (63)
- # onyx (3)
- # pathom (4)
- # re-frame (23)
- # ring-swagger (1)
- # shadow-cljs (49)
- # sql (6)
- # testing (8)
- # tools-deps (45)
- # vrac (1)
- # xtdb (10)
After a bit more thought: FYI for Fulcro users this also wouldn’t break client-side normalization, as your :ident
fn has all of the props available which you queried for: i.e: if you want to have an Account+User
component, which combines :account/id
and :user/id
for instance to enable a :user/id
to belong to multiple accounts. And you don’t want to create ‘syntethic’ ident handling in Pathom like [:account+user/id [42 69]]
then you can write :ident (fn [] [:account+user/id [(:account/id props) (:user/id props)]])
. This way the combination of the system attributes to support client-side normalization stays on the client/Fulcro side, as it should.
(df/load this {:account/id 69 :user/id 42} Account+User)
is how data-fetching would look like