This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # adventofcode (49)
- # bangalore-clj (1)
- # beginners (56)
- # berlin (1)
- # chestnut (6)
- # cljs-dev (5)
- # clojure (48)
- # clojure-greece (29)
- # clojure-russia (3)
- # clojure-spec (5)
- # clojure-uk (3)
- # clojurescript (28)
- # cursive (25)
- # emacs (3)
- # fulcro (123)
- # hoplon (2)
- # klipse (6)
- # off-topic (146)
- # om (11)
- # re-frame (29)
- # reagent (7)
- # reitit (3)
- # specter (11)
- # unrepl (4)
- # yada (3)
@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.
I've added a simple Cursive Github issue related to this. https://github.com/cursive-ide/cursive/issues/1910
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.
It does now actually
@alexmiller Oh nice - so things under
:paths are always source paths? What about resource paths - does it make a distinction?
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.
You can add as many dirs as you like so :paths [“src” “resources” “test”]
Or you can also add :extra-paths in an alias
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.
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.
@alexmiller Is there any plan to be able to get a dependency tree out of deps somehow?