Fluorine Versions Save

Version 4 is now officially released and stable! And it brings a great deal of exciting changes.

Changes

• Compatibility with all ES7 Observable-spec libraries
• Performance improvements and runtime tweaks
• More support for mono-store setups including a new operator
• Middleware!

Specifically there is now a thunk middleware, thunks are not supported by default. There is a distinctSelector operator and a combineReducers helper. And some more minor changes under the hood!

The biggest change are obviously the middlewares. Hopefully this will make it easy to extend and improve on Fluorine in the future!

Please read the docs for the instructions on how to migrate

It has been quite some time since the last release, hasn't it? Hm, 20 days and I go overboard with my emotions for a minor release.

Changes

• Removes shouldComponentUpdate from connectActions and thus from withActions as well, since those shouldn't care about props.
• Added argument pureProps to connectStore and withStore to turn shouldComponentUpdate, which checks for reference equality on the props, on and off. (On by default of course)

Just small things, nothing should break. ?

RxJS Beta 5 broke again, so this temporarily fixes the dependency to version 4 again.

This adds the possibility to use wrapActions recursively.

Updated RxJS to version 5-beta.4

Changes

• connectActions: For completeness sake this adds parity from withStore -> connectStore to withActions. So now you can wrap your actions and inject them using a Provider.

This release fixes some problems with the package.json and updates the dependencies. Please note that starting from this release the npm releases are like the source code now licensed under CC0.

It is recommended to skip any v2 releases as those are unfortunately riddled with buggy edge-cases, that are non-compliant with the v1 behavior.

Changes

• Provider: This is like Redux's Provider. It can pass down an observable and dispatcher to connectStore decorators
• Fix edge cases that broke in v2
• connectStore: Whether you're using a mono-store or a multi-store structure. This should help you to get your structure running easily.
• Rx compliant next method on Dispatcher: It is now discouraged to use dispatch or schedule as next can do everything that these methods can do, combined.

Unfortunately our Ava tests didn't work correctly and weren't covering a huge race condition and the error-catching.

We can tell for sure whether we're 100% fine now after the Ava tests are fixed.

This release turns the dispatcher into an actual Subject. It takes actions, thunks, promises and agendas naturally and makes the dispatcher more composable.