This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-03-06
Channels
- # announcements (4)
- # asami (11)
- # babashka (1)
- # beginners (70)
- # bitcoin (2)
- # calva (68)
- # cider (311)
- # clara (1)
- # clj-kondo (58)
- # cljsrn (18)
- # clojure (37)
- # clojure-australia (1)
- # clojure-europe (22)
- # clojure-poland (6)
- # clojure-serbia (2)
- # clojure-spec (9)
- # clojurescript (11)
- # conjure (4)
- # cursive (16)
- # data-oriented-programming (21)
- # datahike (1)
- # emacs (10)
- # events (1)
- # fulcro (9)
- # girouette (2)
- # graalvm (52)
- # graphql (2)
- # jobs-discuss (5)
- # lsp (8)
- # malli (8)
- # off-topic (17)
- # other-languages (46)
- # pathom (17)
- # portal (2)
- # shadow-cljs (11)
- # slack-help (2)
- # sql (47)
- # tools-deps (14)
- # tree-sitter (1)
- # xtdb (6)
Hey. Is there a trick for getting typehints to things in a go block?
If I put the right hint (I think) where it should go (I think), it doesn't fix things for me.
Oh no.
Ok. Back to promises. Thanks for the swift reply.
Actually, I can just wrap the culprits...
Hi there - any tips for introspecting app state via the REPL when you have 2 browser clients connected? For example, I have a user via regular Chrome window + a second user via incognito Chrome window. The browser runtime for the REPL seems to default to whichever browser client connects first, which makes sense... but I'm curious if it's possible to look at both?
@alex.na you can switch the REPL by specifying the :runtime-id. so (shadow/repl :app {:runtime-id 123})
the runtime id is printed on connect in the console. or you can find in the UI http://localhost:9630/runtimes. inspect and tap> might also be useful