This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-04-13
Channels
- # aleph (1)
- # beginners (105)
- # boot (6)
- # cider (9)
- # cljs-dev (61)
- # cljsrn (59)
- # clojure (132)
- # clojure-germany (1)
- # clojure-italy (6)
- # clojure-russia (18)
- # clojure-spec (1)
- # clojure-uk (58)
- # clojurescript (56)
- # core-async (1)
- # cursive (17)
- # datomic (20)
- # docs (1)
- # duct (5)
- # editors (1)
- # emacs (7)
- # events (2)
- # figwheel (7)
- # fulcro (30)
- # graphql (8)
- # jobs (3)
- # leiningen (23)
- # luminus (14)
- # mount (6)
- # off-topic (41)
- # onyx (14)
- # protorepl (2)
- # re-frame (7)
- # reagent (32)
- # shadow-cljs (236)
- # tools-deps (92)
- # unrepl (8)
- # vim (60)
- # yada (1)
@yogthos I'm in a situation where I'm starting a project and for the first MVP we will only need a small HTTP API that where ring or compjure would suffice. But coming soon we might want to add frontend stuff, and then later a database...i don't want to lein new luminus +all_the_things
at this early stage. What do you recommend to do here?
you could add things in as you go, it mostly involves updating project.clj
later on, but if you fairly sure you'll have cljs on the front-end and a db I'd use +re-frame
and +postgres
(or another db) flags from the start.
Yeah, you should just be able to call run-tests from clojure.test, might make sense to reference it by default in the user namespace
that's the plugin I'm referring to https://github.com/jakemcc/lein-test-refresh