FSM moving out, new build system

Release-1.3.2

Preparing release 1.3.2

1.3.1 Bump dependencies

v1.3.1

Another minor 1.3.1 to bump deps

1.3.0 FSM API iteration and bugs

See changelog for details.

1.2.0 Statecharts

Added

• Integration with https://github.com/lucywang000/clj-statecharts in kee-frame.fsm.beta.

Changed

• Migrated from leiningen and figwheel to deps and shadow-cljs
• [BREAKING] Controllers are now restricted to only returning re-frame dispatch
  vectors. Previously they could return FSM declarations which would implicitly start the FSM.
  That is considered unnecessary implicit magic, as there is not much extra boilerplate in just dispatching
  to the FSM starter.
• kee-frame.fsm.alpha is now deprecated, and will be removed in future versions.

1.1.2 Removed compiler warnings

This is a boring release, upgrading timbre (issue #99 ) to remove some compiler warnings.

1.1.1 Latest expound, remove warnings

Latest controller refactorings introduced a bug that caused warnings on routes without controllers.

1.1.0 Compatibility and performance fixes in re-chain

Re-chain handlers have been updated to conform with re-frame standards for interceptors.

Note that this is a breaking change for users of chain/next feature. That has to be turned back on, see re-chain docs.

1.0.0 With re-frame 1.0.0

This release switches to re-frame 1.0.0. Apart from that, it's mostly about bugfixes and documentation.

The new re-frame version ships with global interceptors. The internals of kee-frame now uses that feature rather than tracking global interceptors itself.

0.4.0 FSM, config, error boundary

New in this release:

• Finite state machine implementation for clearer and more maintainable frontend logic
• New config option for specifying a default redirect route (404)
• Support for overriding re-frame event that handles route changes. Can be used for cases where you need to handle current page state before going to next.
• Updated all dependencies to most recent version
• React error boundary component for catching exceptions in your components without losing control.

Log control, bug fixes

The major new and potentially slightly breaking change in this release it the configurability of logging. Some users might see an error on startup, which should be easily fixable, see docs.