This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # announcements (2)
- # beginners (52)
- # calva (16)
- # cider (5)
- # clj-kondo (1)
- # cljdoc (11)
- # cljsrn (4)
- # clojure (42)
- # clojure-dev (2)
- # clojure-spec (6)
- # clojure-uk (1)
- # clojurescript (18)
- # crux (8)
- # cursive (7)
- # datomic (18)
- # duct (1)
- # fulcro (11)
- # graalvm (1)
- # hoplon (9)
- # leiningen (1)
- # off-topic (8)
- # shadow-cljs (16)
- # spacemacs (9)
- # specter (3)
- # sql (33)
- # vim (3)
Any cool templates (or real projects) for cljs pure libraries (no webapps) with a great development/testing experience?
I seek e.g. source-mapping and a test-on-save workflow which leverages the analyzer cache (my current test-on-save is quite dumb:
git ls-files | grep clj | entr -s "clear; $(which lein) do clean, cljsbuild once test && clear && $(which node) target/out/tests.js")
My cljs knowledge has rusted a little, but from memory, most stuff out there assumes a browser
:node-test target with
:autorun true +
shadow-cljs watch test. see https://shadow-cljs.github.io/docs/UsersGuide.html#target-node-test
I have a question concerning the organisation of web-projects. Is it in clojure a convention to put the frontend and backend into one repository with shared
src folder? If yes, what are the pros? Are there cons? (In comparison with 2 seperate repositories)
Assuming the backend speaks only or primarily to the frontend, keeping them in the same repo offers a number of benefits. One of my favorite being to keep the interface between the two in sync.
I understand. I believe there might be some advantage in keeping a shared spec for data conformity?
In a more complex site, there could also be arguments for keeping them separate. But I'd probably keep them together until those arguments became an issue.
Umm... what sort of a crazy state must I be in if I'm seeing a "Compile Warning, can't take value of macro cljs.core/or" for this code?
(let [a 1 b 2] (cond (or a b) "why am i getting a warning here?"))
@bfay I think thats a known issue in figwheel? IIRC it was fixed but not sure if release yet