This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # aatree (257)
- # admin-announcements (13)
- # beginners (3)
- # boot (327)
- # cider (2)
- # cljs-dev (1)
- # clojure (127)
- # clojure-art (72)
- # clojure-russia (273)
- # clojure-sg (1)
- # clojurescript (39)
- # cursive (8)
- # datomic (6)
- # editors (2)
- # emacs (4)
- # hoplon (261)
- # immutant (2)
- # ldnclj (15)
- # liberator (10)
- # luminus (1)
- # off-topic (8)
- # om (9)
- # parinfer (1)
- # re-frame (11)
- # reagent (2)
- # yada (9)
Can you share some cljbuild configuration across all builds instead of duplicating it?
jindrichm: with lein? yes, via profiles: https://github.com/technomancy/leiningen/blob/master/doc/PROFILES.md
@darwin: Yes, with lein. Does cljsbuild merge configuration from profiles and builds based on shared ID?
yes, here is an example how I used it recently: https://github.com/binaryage/cljs-devtools-sample/blob/master/project.clj
the trick is to use map form for
:cljsbuild configuration, maps are merged automatically
see the comment: prevent https://github.com/emezeske/lein-cljsbuild/issues/413
it is not necessary, just reduces warnings when this project is used in checkouts of other project
warning: unfortunately implicit rules for built-in leiningen profiles are quite complicated, so you should avoid naming your profiles the same way, it leads to unexpected behaviour
@spacepluk: “some situations” is vague, if you have minimal case share it so it can be examined
@dnolen for now it seems to be only that case I mentioned, I'll setup a simple test case tomorrow.
@spacepluk: will definitely want to see a minimal case for this, in general case source maps work great
I am trying to port spit+slurp to node and cannot get with-open to work. I am trying to writing the macro in cljc so it can throw a js/error, but I cannot get it to work. https://gist.github.com/anonymous/4e7a7c13167f86d3c67a
I've tried requiring it a bunch of different ways. I think defmacro may work differently in cljc?
To clarify with an example, I'm creating a login dialog. Trying to log in runs a remote mutation. How do people handle the case when that mutation fails due to, for instance, a bad username/password combination?
Do you mutate a :login/error field in the state atom, or do you throw an alert box, or what?
I think om.next's way of dealing with state is good, I'm just confused on how to handle stuff like this. In reagent/re-frame I would normally perform the http request, and then mutate the app state based on the response, so this is new territory for me.
@rhansen: you might want to try asking over in #C06DT2YSY. I don’t have an answer but I’d be interested to hear one.