Skip to content

Releases: AlexGalays/fluxx

0.14.1

29 Mar 21:34
Compare
Choose a tag to compare
  • (Re)introduce transient stores. Turns out 100% global state is very naive.
  • Better typed Store style for typescript (or JS)

0.13 - Complete redesign

09 Feb 09:49
Compare
Choose a tag to compare

This new design takes heavy inspiration from Elm/redux while also making native support of typescript a forethought.

There is now only one store in an application using fluxx. After writing a React app where the choice between states, props and multiple stores is not always easy, plus the will to support typescript, this became a mandatory move.

Compared to redux, fluxx trades some tooling/serialization support for much terser code.

List of changes:

  • Only one store singleton. Remove ActorStore
  • Logging is now enabled with Store.log = true
  • Add native support for typescript
  • Move to babel 6 -.-

0.12.3

01 Dec 18:26
Compare
Choose a tag to compare

Bug fix : ReactConnector's stores created from factories were never disposed

0.12.2

19 Oct 11:51
Compare
Choose a tag to compare

Fix Store when its state is an Array

0.12.1

17 Oct 09:07
Compare
Choose a tag to compare

ReactConnector
- Can now take a Store factory
- Only allows a single child function as static children relying on external state is dangerous

Async action documentation

0.12.0

07 Oct 21:30
Compare
Choose a tag to compare

ReactConnector changes only:

  • Use React 0.14.0
  • Delete shouldComponentUpdate optimization : There are many cases where this can be invasive.

0.11.0

25 Aug 09:37
Compare
Choose a tag to compare

Prebuild the ES6 codebase so that users are not forced to use a particular browserify transform /webpack loader / etc setup.

0.9.0

06 Aug 07:39
Compare
Choose a tag to compare

Added React Connector addon

ES6 rewrite

0.8.0

02 Aug 21:29
Compare
Choose a tag to compare

Added a new Store style

[Breaking changes] Imports

  • Store has been renamed to ActorStore.
  • onChange is no longer attached to the Store object but to the fluxx object.

0.7.0

01 Aug 22:27
Compare
Choose a tag to compare

[Breaking change] Action handlers must now return fluxx.NO_CHANGE instead of false is they wish to prevent the change event from being dispatched.

This change was made as it's easy to inadvertently return false in ES6:
on(reset, () => flag = false);

It's also more explicit.