This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # adventofcode (20)
- # babashka (118)
- # beginners (170)
- # calva (1)
- # clojure (102)
- # clojure-europe (1)
- # clojure-nl (13)
- # clojure-uk (5)
- # clojuredesign-podcast (19)
- # code-reviews (10)
- # core-async (9)
- # cursive (7)
- # datomic (8)
- # fulcro (3)
- # malli (5)
- # mount (1)
- # off-topic (19)
- # overtone (1)
- # reagent (2)
- # reitit (2)
- # spacemacs (2)
- # sql (4)
- # tools-deps (5)
Hello, I would like you to give me feedback on a new web framework I am developing. I've posted a cut-down version for small jobs. Thanks in advance.
I think you might want to reconsider your choice of namespace leiningen.new.tadam-lite, since it gives the impression that this is part of leiningen.
It's probably necessary to write some explanation of what the library does or example usage or something
@eric.d.scott That's the namespace
lein new expects -- that's how you write Leiningen templates.
It is part of Leiningen in a way, because it's a template that
lein new (or
boot -d boot/new new or
clj -A:new) know how to read and create a new project from.
And here it is on Clojars https://clojars.org/tadam-lite/lein-template with the group ID
tadam-lite and the required artifact ID
Boot templates all have an artifact ID of
boot-template and will have
boot.new.* in their namespace name. CLI/`deps.edn` templates will all have an artifact ID of
clj-template and will have
clj.new.* in their namespace name -- although
clj -A:new can also use local templates on disk and projects in a git repo: they don't need to be published to http://clojars.org.