bind-handler
now requires an event-flags map as its second argument, and accepts supplimental arguments that will be passed to the handling function. So (bind-handler #{} myfn 1 2)
will call (myfn state event 1 2)
:advanced
compilation mode of the precompiled templates from 50kb to 8kb.target/
and to example/
so lein doesn't clobber it on buildslist
: not sure why you'd need this, but it becomes a fragmentdo
, for
, let
, if
(and its ilk), when
(and its ilk), case
, cond
have their expressions parsed
I havent' ever needed to use threading macros in the process of constructing a view, and feel supporting those
is not worth the effort at this point.use-atom
that doesn't make a new atom on every changebind-handler
whichs takes an atom, an optional set of event-processing flags, and a processing function,
and swaps the contents of the atom with the processing function, perhaps stopping or extracting the event's target first.on-input
to onInput
anymore. Perhaps it could be done for DOM elements and not JS components, but the inconsistency would bug me. We'd have to offer a way to supplant the built-in transforms, and then they couldn't be done at compile-time. I feel this is one of those things better shoved into the face of the library consumer.precog/use-js-props
Can you improve this documentation?Edit on GitHub
cljdoc is a website building & hosting documentation for Clojure/Script libraries
× close