On Monday, March 23, 2015 at 8:40:37 PM UTC+11, Karsten Schmidt wrote: > Hi Mike, is that by any chance meant for re-frame? If so, I've got an updated > fork with refactored logging using cljs-log[1] and will send PR later today... > > Cljs-log fully elides logging calls at compile time based on log level > (configurable via env vars) > > Hth! K. > > [1] https://github.com/postspectacular/cljs-log >
Hey Karsten, Thanks, that looks interesting. Would be very nice to be able to set log levels in build spec. There has been limited discussion on this already, but it has a debugging flavour, rather than a logging flavour (subtle differences): https://github.com/Day8/re-frame/issues/34 Back to this macro ... No, this is not for re-frame, but instead for use in "re-com" which is an upcoming set of reagent components (will only work with a modern browser -- so it will be useful for enterprises app perhaps, or when you are doing atom shell work). Anyway, re-com checks all params very carefully in dev mode, but we need those expensive checks gone for production. That's what I'm chasing here: a way to use goog.DEBUG in a macro (and using goog.DEBUG requires that ^Boolean metadata). Thanks, Mike -- Note that posts from new members are moderated - please be patient with your first post. --- You received this message because you are subscribed to the Google Groups "ClojureScript" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/clojurescript.
