This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2023-03-30
Channels
- # aleph (2)
- # announcements (8)
- # babashka (12)
- # beginners (34)
- # calva (36)
- # cherry (3)
- # cider (1)
- # clj-kondo (11)
- # clj-otel (6)
- # cljdoc (31)
- # clojure (121)
- # clojure-conj (1)
- # clojure-czech (2)
- # clojure-europe (109)
- # clojure-nl (1)
- # clojure-norway (5)
- # clojure-uk (3)
- # cursive (3)
- # datahike (1)
- # datomic (9)
- # deps-new (6)
- # docker (5)
- # emacs (21)
- # fulcro (4)
- # hoplon (16)
- # introduce-yourself (2)
- # london-clojurians (5)
- # lsp (87)
- # malli (17)
- # missionary (1)
- # nbb (27)
- # off-topic (257)
- # pathom (4)
- # portal (42)
- # practicalli (1)
- # rdf (3)
- # releases (2)
- # shadow-cljs (49)
- # slack-help (3)
- # timbre (2)
Hey guys, I hope you're doing well. My name is Ítallo, I'm a developer... I wanted to clear up a doubt, how do I point the "clj-otel-api" locally, without using "com.github.steffan-westcott/clj-otel-api "0.1.5"", to test before uploading a fork
Include the dev
alias when launching the REPL to use local source code rather than released modules. This is covered in the https://github.com/steffan-westcott/clj-otel#developing.
@U2C6SPLDS but can i do it using docker?
Use whatever your normal development process provides for starting a REPL. Somewhere you need to specify what aliases to enable. For example, I use Cursive which has an aliases option as part of the run configuration.
I followed the documentation, I added a "dev" aliases with override-deps and I'm running lein for dev, but it doesn't work lol