This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-02-26
Channels
- # aws-lambda (2)
- # beginners (10)
- # boot (17)
- # cider (19)
- # clara (1)
- # cljs-dev (13)
- # cljsjs (22)
- # cljsrn (1)
- # clojure (132)
- # clojure-austin (2)
- # clojure-berlin (2)
- # clojure-dusseldorf (1)
- # clojure-germany (2)
- # clojure-italy (7)
- # clojure-spec (6)
- # clojure-uk (5)
- # clojurescript (45)
- # core-matrix (3)
- # cursive (4)
- # datomic (8)
- # emacs (3)
- # keechma (3)
- # lein-figwheel (1)
- # leiningen (2)
- # lumo (24)
- # nyc (1)
- # off-topic (29)
- # om (68)
- # onyx (5)
- # perun (50)
- # planck (5)
- # protorepl (5)
- # re-frame (128)
- # reagent (10)
- # remote-jobs (1)
- # ring (4)
- # rum (41)
- # untangled (28)
- # yada (4)
i.e. if the response is not json, does it throw an "Uncaught SyntaxError: UNexpected token : " ?
when using cljs-ajax, I am getting (in my :handler) something like this:
["^ " "~:attributes" ... ]
when I'm expetcing something like
{:attributes ... }
I have tried specifing the :format as :json and as :transitapaprently (. resp setContent TYpe "application/transit+json") fixed it , though no idea why
am i doing something wrong with re-frame here: https://hastebin.com/ofaruyewiq.lisp ? only the inner function in post is re-rendered when post-ids is updated which leads to the wrong data being showed in
@post
.Try this:
(defn post
[post-id]
(let [post (re-frame/subscribe [:post post-id])]
[:div (:id @post)]))
If that fixes the problem, see this issue and note the explanation for "Corner Case #1" https://github.com/Day8/re-frame/issues/218#issuecomment-252470445
this worked. thanks a lot! i will read the explanation to better understand what i did wrong.
besides :optimizations ;advanced, are there any other mode that outputs just one .js file instead of a bunch of .js files ?
@qqq https://clojurescript.org/reference/compiler-options#optimizations :simple
and :whitespace
@briank42 there is a #re-frame channel
@lgessler have you checked #beginners ?
hey guys, has anyone tried the latest clojurescript + core.async under :advanced? I鈥檓 pretty positive it is broken, I made a minimal case https://github.com/raspasov/cljs-1.9.494-core-async-broken
it has been reported, but thanks for putting a minimal case together
Please use 1.9.473 for now
I鈥檓 not successfully able to get any errors when I pass functions bad arguments, and can鈥檛 find any examples of folks using spec in cljs
FYI, if anyone has a library dependent on core.async, you could throw in a code like this to warn unsuspecting people upgrading to .494: https://github.com/binaryage/chromex/commit/e904441b73e9c5db12a56d4d0fd86ffecfb1fb3a
I'm not sure that would work with Boot
why not just check *clojurescript-version*
?!
I just googled for detecting clojure library dependency version and this was the first thing that came out, didn鈥檛 think about it more
here's how we do it from a macro in Om
@anmonteiro thanks! got it 馃檪
Hi I have a question about the eventual deployment of my app. Do most people simply do lein uberjar, move the jar over, and lein it? I am wondering what people do when they update their cljs (so the javascript file) but the backend does not change...
can someone pls patch #js so that: :stroke-width -> strokeWidth :font-size -> fontSize :pointer-events -> pointerEvents otherwise, #js is forcing me to use camelCase 馃槥
@qqq not gonna happen
what if you actually want a JS object with font-size
or something?
#js
is about interop
keywords and strings mean the same in #js
they're ultimately converted to strings
#js {:a 1}
is just sugar for (js-obj "a" 1)
if you want that behavior in e.g. Om you can use https://github.com/plumatic/om-tools