flummox - npm Package Versions

3.3.0

• New Feature
  • registerAll() and registerAllAsync() @hugobessaa

3.2.1

• Bug Fix
  • Fix connectToStores HoC to pass state instead of props.

3.2.0

• New Feature
  • New higher-order component connectToStores, because why not. It works just like FluxComponent.

3.1.2

• Bugfix
  • Switch back to using cloneWithProps() instead of cloneElement() to fix context passing with FluxComponent. See this issue for an explanation.

3.1.1

• Bugfix
  • Add dummy handler to internal promise to prevent false warnings.

3.1.0

• New Feature
  • Flux is passed as second parameter to custom render function of FluxComponent.
  • New Store method getStateAsObject() is used inside default state getters for connectToStores(). This should be overridden alongside Store.assignState().
  • New prop stateGetter for FluxComponent. (@tappleby)
  • Store no longer warns if setState() called outside dispatch handler. There are some valid reasons you may want to do this, primarily tests.
• Internal
  • Updated dependencies.

3.0.1

• Bug Fix
  • Add Store.assign() workaround for TypeScript, since it doesn't support extending static methods. (@ivw)

3.0.0

• New Feature
  • Transactional state updates: this.setState(state => ({ foo: state.foo + 1 })).
  • A new static method Store.assignState() can be overridden to customize the top-level state type.
  • Custom rendering in FluxComponent. Pass a function as the render prop.
• Breaking Change
  • FluxComponent and fluxMixin require React 0.13.
  • Stores no longer use empty object as default state. Default state is null, like React.
  • The array form of connectToStore() accepts a single state getter as the second parameter, which is passed an array of stores corresponding to the passed keys.
  • State getters are no longer auto-bound to the component. Props are passed as the second parameter.
  • Directly-nested FluxComponents warn about mismatched parent and owner context. Not sure how to fix this yet, but it will work because of prop transfer, anyway. To avoid the warning, use render prop instead.
  • connectToStores() no longer checks if component is mounted before updating, since isMounted() is deprecated in React 0.13. 99% of the time, this shouldn't be a problem, and it's easily worked around using the render prop. Let me know if this is a serious issue for you.
  • FluxComponent updates in componentWillReceiveProps() instead of componentDidUpdate(), preventing extra render.
• Internal
  • Remove undocumented method Store#getState().
  • Favor const over let.

Big thanks to @tappleby, @hugobessaa, @gaearon, @emmenko, @ariabuckles, and everyone else who submitted a PR or an issue or contributed in any way.

2.13.1

• Bug Fix
  • Small update to async actions so returned promise does not reject due to errors that occur in store handlers.