This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-07-10
Channels
- # announcements (3)
- # architecture (54)
- # babashka (11)
- # beginners (12)
- # calva (5)
- # clj-on-windows (1)
- # cljdoc (2)
- # cljs-dev (1)
- # cljsrn (6)
- # clojure (130)
- # clojure-europe (8)
- # clojurescript (21)
- # conjure (23)
- # core-async (4)
- # datomic (7)
- # depstar (77)
- # events (1)
- # fulcro (27)
- # lsp (88)
- # malli (5)
- # meander (1)
- # off-topic (4)
- # pathom (43)
- # polylith (39)
- # re-frame (9)
- # shadow-cljs (14)
- # timbre (3)
- # tools-deps (53)
It also allows aliasing, so if you have the alias [bar.baz :as b]
then ::b/foo
resolves to :bar.baz/foo
so how do I query this?
(pc/defresolver cursos-alura [env _]
{::pc/output [{::cursos-alura [:curso/id]}]}
{::cursos-alura [{:curso/id 1}
{:curso/id 2}]})
No, ::cursos/cursos-alura
literally equals :aplicacao.resolvers.alura.cursos/cursos-alura
If you want it to be :cursos/cursos-alura
, then you should make that the key of your defresolver
"If you want it to be `:cursos/cursos-alura`, then you should make that the key of your `defresolver` " -> Understood
when running from Clojure you need to quote it, otherwise it tries to invoke the keyword: ['(::instruments {:sort :instrument/brand})]
How much work is it to migrate from v2 to v3?
depends on what you use from Pathom 2, resolvers are mostly compatible (in terms of definition, the major difference is that inputs are now EQL instead of sets). plugins also require change. I'm going to start working on a "portability library" this week, I wanna see how automatically we can make it, the idea is to have a different namespace that you require and you use the same Pathom 2 interface to use Pathom 3 implementation