New API:
add-post-event-callback
to the API.
@pupeno is developing prerenderer which looks pretty neat.
Support this effort by adding a way for prerenderer to hook event processing.on-changes
middleware now official. No longer experimental.Improvements:
New Features:
Improvements:
fixed problem with log grouping
removed -------New Event-------
log msg
made groups collapsed by default
#104 - Updated to the latest TodoMVC CSS
Reimplemented the router loop. Removed use of core.async. Replaced with hand rolled scheduling. See 420e42a As a result:
dispatch
and the associated event handler being run. (<1ms vs 5ms??)This fixes issues like #39 and #121
I doubt this will affect normal apps. But it could affect games which depend on existing timings. Maybe. It could affect apps which dispatch large volumes of events (telemetry?) very quickly. Maybe.
Improvements:
examples/
now work with figwheelHeadline:
Deprecated:
log-ex
middleware is no longer needed. Simply remove its use.
Sometime in the last couple of months, changes to the CLJS
runtime meant that useful exceptions could escape go-loops, and
good stack traces appear (at least in Chrome).New Features:
(dispatch [:purge-redos])
When trying to recover from an UHE, do an undo to get back to the
last sane state, and then use this new feature to purge the
just-generated-redo.Experimental:
on-changes
.Other:
Improvements:
Various small improvements and bug fixes:
after
and enrich
now call the supplied function f
with
both db
and v
(previously just db
). Because javascript is so forgiving
about function arity, this change is backwards compatible.log-ex
for correctly printing handler stacktraces.
See explanation.Renames:
register-pure-handler
renamed to register-handler
(and existing low level register-handler
becomes register-handler-base
but is not a part of the API).apply-event
middleware and replace with similar trim-v
register-subs
to register-sub
(avoid confusion over possible plurals)set-max-undos
to set-max-undos!
Changes:
undoable
middleware is now a factory. Where before you used this undoable
,
you must now use this (undoable "some explanation")
. See further below.todomvc
available in examples folder.debug
, enrich
and after
The undo/redo feature built into re-frame is now more functional (at the cost of a breaking change).
There is now an explanation associated with each undo state describing modification. This allows an app to inform the user what actions they will be undoing or redoing.
Previously undoable
was simply middleware, but it is now a middleware factory.
Essentially, that means you can't use it "plain" anymore, and instead you must
call it, like this (undoable "Some explanation")
The explanation
provided to undoable must be either a string
(static
explanation) or a function (db event) -> string
, allowing you to customize
the undo message based on details of the event.
Initial public release
Internal beta release
Can you improve this documentation?Edit on GitHub
cljdoc is a website building & hosting documentation for Clojure/Script libraries
× close