Fork me on GitHub
Oliver George02:12:51

@cfleming just checking where Cursive stands regarding deps.edn support. I couldn't see a github issue covering it.


@olivergeorge No, there’s no support yet, or an issue I can recall


Feel free to file one, I’m planning to add support at some point but I haven’t figured out the priority yet.

Oliver George00:12:11

I've added a simple Cursive Github issue related to this.


Great, thanks!

Oliver George09:12:46

Thanks, will do. It’ll be nice to have a simple / barebones tooling option.


@olivergeorge Sure. There are some issues with it - deps has no concept of source folders, for example. I’m not sure how I’m going to handle that.


@alexmiller Oh nice - so things under :paths are always source paths? What about resource paths - does it make a distinction?

Alex Miller (Clojure team)22:12:44

From a classpath perspective, there is no difference


Right. I’ll need to figure out how to handle test paths and so on as well, it’ll probably just need some UI around it.

Alex Miller (Clojure team)23:12:06

You can add as many dirs as you like so :paths [“src” “resources” “test”]


Right, but IntelliJ likes to know which is which.

Alex Miller (Clojure team)23:12:41

Or you can also add :extra-paths in an alias


And the example in the README suggests putting test in an alias

Alex Miller (Clojure team)23:12:00

So you could create aliases for each and selecting them


Right, but I need to be able to read any deps file and figure out what the user’s intention was.


So I can’t force them to use a particular alias layout.


I guess I’ll present a list of all source paths found in all aliases, guess based on whether they’re called “test” and then let the user customise the result.


Or something similar.


@alexmiller Is there any plan to be able to get a dependency tree out of deps somehow?


AFAICT it will only return a classpath right now.