This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # aws-lambda (21)
- # beginners (8)
- # boot (67)
- # braveandtrue (2)
- # cider (12)
- # cljs-dev (38)
- # cljsjs (87)
- # cljsrn (11)
- # clojure (307)
- # clojure-austin (29)
- # clojure-finland (1)
- # clojure-italy (9)
- # clojure-russia (19)
- # clojure-spec (71)
- # clojure-uk (33)
- # clojurescript (109)
- # clojutre (1)
- # core-async (2)
- # cursive (24)
- # datomic (11)
- # devops (5)
- # ethereum (5)
- # figwheel (2)
- # hoplon (25)
- # ipfs (1)
- # jobs (1)
- # luminus (17)
- # off-topic (1)
- # om (38)
- # om-next (3)
- # onyx (166)
- # other-lisps (1)
- # proton (5)
- # re-frame (15)
- # reagent (45)
- # ring (2)
- # spacemacs (6)
- # specter (12)
- # untangled (58)
- # yada (23)
Here's the blog post I was promising someone a while back, complete with some code samples (and a bit of selling for our coworkers who haven't seen live-reloading in action): http://tech.adstage.io/2016/09/12/how-we-test-full-stack-clojure.html
@therabidbanana: Really interesting post, I think it's worth posting to some non-untangled channels as well - lots in there that applies to pretty much every front end CLJS project.
Good job. So u guys are using boot instead of leiningen. Great! Any ideas to share the experiences?
I think that'd probably be something worth writing up, but I'm more of a clojure newcomer so I haven't really dealt with leiningen all that much for comparison
Doesn't look like it takes much advantage of being in boot from the looks of the build.boot file - we have a lot more in our actual project. Might be worth updating a bit.
Hey @baris I've actually got a boot-untangled template in the works. I'll post it here as soon as it's ready!
@currentoor: I’ve already got untangled-template going, have you looked at that and/or is there a reason you couldn’t put boot in that?
@ethangracer it's kind of funny the devcards visual regression test idea were the direct result of spite and anger with a former teammate rather than some good idea we deliberately cooked up
i basically got furious one night and had to prove the clojure stack was worth us using 😄
yeah, new obscure frameworks are a tough sell. I was exploring the competition today...still not seeing anything I like nearly as well. I know I'm biased, but the full-stack story we have is pretty darn compelling once you understand it.
anyone playing with anything to componentize CSS with respect to their Om/Untangled components?
I've been brainstorming on that particular topic because we're starting an untangled-components library, and I want people to be able to style the things easily.
I've got a meeting to go to now, but if anyone has ideas, feel free to share them here or in PM
yeah, co-located CSS? Compiler integrations the extract base CSS like the i18n stuff? Naming conventions with CSS name generation macros, etc.
I'm trying to weigh the different options and see what seems to have the best long-term promise
Other approach would be use something like garden, I've played with that recently, not too bad to use (but in CLJ, not sure if it works well in CLJS)
Now that our designer is getting more into the CLJS files maybe we can subject him to a few experiments.
I understand. I'm wondering how well that can be made to work where you have components some CSS person is trying to style
generated classes are ns-name prefixed by default, but you can specify raw classes without prefixes