This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2023-01-26
Channels
- # aleph (9)
- # announcements (31)
- # babashka (23)
- # beginners (35)
- # biff (2)
- # calva (5)
- # cider (10)
- # clara (11)
- # clerk (114)
- # clj-kondo (18)
- # cljdoc (37)
- # clojars (7)
- # clojure (24)
- # clojure-austin (10)
- # clojure-europe (27)
- # clojure-nl (1)
- # clojure-norway (23)
- # clojure-uk (2)
- # clojurescript (18)
- # conjure (2)
- # core-async (6)
- # cursive (21)
- # datomic (3)
- # fulcro (15)
- # introduce-yourself (7)
- # lsp (32)
- # malli (57)
- # meander (5)
- # music (1)
- # nbb (2)
- # off-topic (17)
- # pathom (6)
- # rdf (4)
- # reagent (8)
- # releases (2)
- # shadow-cljs (4)
- # slack-help (23)
- # spacemacs (6)
- # tools-build (32)
Thanks a lot for these, Wilker! > ERROR: “Resolver :order/name-resolver returned an invalid response: “some text” I keep forgetting to return a map 😅 and this always saves me 🙏
I see there’s a plugin entry point for ::pcr/wrap-resolve
which provides access to the input
. Is there a way to access the output
that’s being used to identify the resolver? Or is there a way to get access to the resolver’s symbol? Basically I’m looking for a way to identify the resolver itself. (This is to tap into our own performance profiling mechanisms.)
yes, trying to remember from the top of my head, but I think on env
you should be able to find a ::pcp/node
, which is planning node, that includes the op-name
also includes what specific parts are being looked at for that specific call, in the ::pcp/expects
key in the node map, but you can also get the full one looking at the index using the op-name
Okay, that’s wonderful. I think I see it in here.