I am looking at adding something like Cider Jack-in to Calva. (Too many Calva users stumble on the dependency problem.) A question to Emacs/Cider users. Is there something you need to do to configure jack-in per project, or does Cider figure out things for you? Are there different jack-ins for figwheel and shadow-cljs users and how about clj/leiningen/boot?
No configuration needed for Emacs. I think there's a prompt when you jack in with cljs to ask whether you're using figwheel, shadow, etc.
Vim jack in is more explicit, it doesn't try and figures out the project type by looking for certain files. It just gives you a few commands to do different things.
Thanks, @dominicm. I think I have tricked myself into this ”figuring out” thing and it works quite well for some limited number of options, but gets brittle quickly. Prompting is a quite common Ux pattern in VS Code, so I might go that way. Great, now it doesn't look so hard to implement.
curious what from your POV is brittleness, I've found the cider-jack-in injecting dependencies avoids the brittleness because your version of your edit plugin works well with which nrepl/middleware. calva would benefit here as well (i.e. never having to tell users to bump the version of cider-nrepl in their profiles.clj/project.clj) -- because the versions are in sync