Chas Emerick
Chas Emerick
I'm currently using `Unsafe.data` to bring known-good HTML fragments (produced by a reasonable markdown->HTML generator) into the tyxml world. AIUI, that _should_ be okay, but perhaps the current issue demonstrates...
Insofar as many (some?) applications consuming JSON are at peace with presuming floats everywhere (given the Javascript heritage), an option to only ever emit `` `Float`` values for numbers (and...
Much of the existing test suite consists of tautological / information-sparse checks, e.g. "was this function called with these 8 arguments?" IMO, it's not useful to check that calling one...
(…and it's at least partly my fault! :-|) The typical way to use a private/fork build of a library in leiningen is to: 1. Put the artifact on e.g. clojars,...
Leiningen hooks are semi-deprecated, in favor of `:prep-tasks`. cljsbuild should follow suit, and recommend their use instead of trying to be clever about automagically doing stuff.
In short, usage of custom tagged literals (aka "data readers") works as expected using `cljs.build.api`, but fails under cljsbuild. A reproducing project is available here: https://github.com/cemerick/failing-cljsbuild-data-readers Using `cljs.build.api`: ``` $...
The set of scripts in `./bin` are more than a little crazy. :-)
Given the perf I'm seeing of the current manual mtime "watch" approach (only post-gh-219), I'm currently unconvinced of the need for inotify-style watching. References to cljs projects that exhibit poor...
Per https://github.com/emezeske/lein-cljsbuild/issues/293#issuecomment-34555946, this is not going to be checked in the CLJS compiler.
First, thank you so much for this ppx, it makes working with postgresql in OCaml extremely pleasant :hugs: I am regularly running into cases where I need to emit [multiple...