Hi! In ES6, having 3 variables, I can do { msg, status, env } and get { msg: msg, status: status, env: env }. Is there a similar trick for clj(s) (other than writing my own macro or defining a record with these field) to do that or do I need to manually write { :msg msg, :status status, :env env }? Thanks! #DRY

nothing like that in standard CLJ/CLJS no

if you can do that, it means that data is already somewhere. if that "somewhere" is a map, do this: (select-keys data #{:msg :status :env})

Is cljs.spec.alpha a part of latest clojurescript and I can just require it or is it a separate lib? Couldn't find it on clojars/maven?

(ns some.cljs.project
  (:require [clojure.spec.alpha :as s]))

works for me:D

@holyjak it is part of cljs itself yes

How do I work with js functions that return promises in cljs?

@pablore just handle the promise as in js (-> p (.then do1) (.then do2))

thanks

also take a look at promesa library http://funcool.github.io/promesa/latest/

how to translate this into clojurescript document.querySelector ('.app') ?

(js/document.querySelector ".app")

I was thinking about using the expectations library in an atom validator during development. Question: what’s the normal (simple) way of ripping the library and validators out of production?

i guess it’s sort of a dumb question. in node, there is a de facto practice of setting NODE_ENV=production and lots of libraries follow that. my question is really: is there a similar practice here?

does clojurescript allow turning assertions off in the same way clj does?

oh, you want to remove the whole library too?

that would be nice given that code size matters

obviously i could just cook up something myself by setting a variable and not using the library. i could then either hope that the optimizer kills the unused code or figure out some kind of reader macro thing to remove the require statement (i have no idea how to do that so that’s why i’m asking if there’s an obvious easier way)

if it doesn’t exist yet it would be really cool to see it implemented

well the cljs assert macro uses *assert*, which is set with a compiler option, to remove assertions. it says not to use “manually” but I think that means don’t set it manually. reading it to do development-only validations makes sense to me.

#js is a reader macro right? what cljs function is closest in functionality ?

is clj->js what you're looking for?

I'm seeing some cljs compilation behavior that I don't understand, hoping someone here can help me out. With clojurescript 1.9.946 and tools.reader 1.1.0, I'm seeing the "no reader function for tag Inf" problem described here: https://stackoverflow.com/questions/48039878/cljs-core-cljs-line-988-col-14-no-reader-function-for-tag-inf. I upgraded tools.reader to 1.2.1 and that issue went away. Now I'm getting the invalid js output issue described here: https://dev.clojure.org/jira/browse/CLJS-2352. I'm not sure what I've got wrong, since the dependency versions are right. I verified dependency versions using lein deps :tree - if there's a better way to check the versions please let me know.

nvm, blowing away target directory solved the problem.