I'm also betting that defaulting to "app" rather than core doesn't work for you either

People should be explicit about their project namespace.

and my point of view is that the name in the template can be more general than a project name, and it can be helpful to let folks who write templates do what they want.

the clj generators come in handy there

Just a heads up, I pushed a new https://github.com/hagmonk/depify that now includes the ability to read project.clj from stdin, as well as interpreting output from lein pprint

Hey so riddle me this ... has any thought been given to using deps.edn in the context of a monorepo?

I’m not sure it’s currently possible to supply a path to a directory inside a larger git repo - perhaps I just missed that feature?

We're working with a monorepo at work and slowly figuring that out. Not a priority tho' so progress is a bit slow.

as a git dep or a local dep?

there are some ways with :deps/root etc to do some of this but also some known issues

I'm working with local deps so far.

I guess in the context of the monorepo itself, you would use :deps/root to point at other resources in the monorepo ... but clients outside the monorepo have no way to point at a subfolder’s deps.edn

A real world example would be figwheel-main’s deps.edn: https://github.com/bhauman/lein-figwheel/blob/master/figwheel-main/deps.edn

AFAICT, there’s no way I can depend on that deps.edn file, because it’s not at the root of the repo

@hagmonk Setting :deps/root to "figwheel-main" doesn't work?

Oh, perhaps that is the thing I’m missing!

{:git/url   ""
 :sha       "6368c0e49108fc7a8ec99df05831ff289123f1a5"
 :deps/root "figwheel-main"}

Thanks @kenny! Had no idea that existed

Yeah I had the same problem. I don't think it's documented yet.

it’s not

good to know!