Fork me on GitHub
#cider
<
2021-08-04
>
jmckitrick02:08:13

@vemv The docs say it's a library as well. How would it be used with tools/deps (without Leiningen)?

vemv02:08:43

I have an issue open for that It's doable, I have a plan. I should just get to it some weekend. Feel free to nudge me over the issue tracker if too much time passes

vemv02:08:07

btw PR welcome if anyone wants a deps.edn adventure... it's kind of low-hanging fruit I actually use deps.edn frequently / at work. My workaround is slurping deps.edn from Leiningen. I like all my tooling lein-based even when using deps.edn

jmckitrick11:08:54

I'm curious to know how you do that. I've always used Leiningen, but my new job uses deps.edn. I haven't dug into the interop. Once I got CIDER working with front and back end, I moved on....

vemv11:08:01

I use this generic project.clj that will work with most deps.edn files out there. There can always be edge cases though :) https://gist.github.com/vemv/7239033e8a16f2cc24b32f637bf42959 This approach is superior to the plugins you can find out there IMO. If something goes wrong you can add a println and fix it immediately I have a bash wrapper for lein that will copy this file to $PWD if no project.clj was found

jmckitrick12:08:49

Pretty slick! I'll have to try it out....