This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-02-14
Channels
- # announcements (4)
- # aws (7)
- # babashka (44)
- # beginners (178)
- # calva (15)
- # cider (3)
- # clj-kondo (15)
- # clojure (139)
- # clojure-dev (8)
- # clojure-europe (2)
- # clojure-italy (2)
- # clojure-losangeles (9)
- # clojure-nl (32)
- # clojure-spec (6)
- # clojure-sweden (1)
- # clojure-uk (27)
- # clojurescript (17)
- # core-typed (116)
- # cursive (26)
- # data-science (1)
- # datomic (14)
- # duct (16)
- # emacs (9)
- # events (1)
- # fulcro (47)
- # jobs (3)
- # juxt (6)
- # keechma (2)
- # malli (59)
- # mid-cities-meetup (8)
- # off-topic (32)
- # pathom (5)
- # reagent (2)
- # remote-jobs (4)
- # rewrite-clj (16)
- # shadow-cljs (14)
- # spacemacs (9)
- # sql (27)
- # tools-deps (37)
- # vscode (7)
In the Pathom visualizer, what are "Attributes with type mismatch"?
in this context, the different types are scalar
vs link
, so for example, if one resolver you have something like ::pc/output [{:user/main-address [:address/id]}]
it will consider :user/main-address
a link, but if later another resolver says ::pc/output [:user/main-address]
, that's a scalar, now you have a mismatch, because the data should be consistent, the fix is to find the scalar version and declare what comes inside (or change the name in case they are really different things), makes sense?
Alright. So far, I have lots of maps. I have been sometimes using the link
notation to drill deeper into their fields, and sometimes not. Should I be saving the link
notation for only cases where the results are a collection of items and perhaps some other uses?
I.E. When pulling apart a map, should I always simply do so as a scalar
+ a separate resolver, instead of sometimes using link
s?
the more you can inform to pathom, the better, so on every map, if you can know the structure of, better to express it in the ::pc/output