0.13.2

• Fixed lost state update when listener dispatches an action on Cursors.forEach.
• Fixed processor to fail on projects without AutoValue in classpath.

0.13.1

• Rebuilt libraries with the latest version of Retrolambda (2.4.0).
  No need to add retrolambda-related proguard rules anymore.
• For a processor, made a dependency to auto-value compile only.

0.13.0

New Module: ReductorObservable

Added ReductorObservable module that mimics redux-observable.
This allows to dispatch async actions and do side-effects in a composable way using RxJava.

0.12.0

New feature: Dispatcher and Cursor

Introduced two interfaces, both implemented by Store:

public interface Dispatcher {
    void dispatch(Object action);
}

public interface Cursor<State> {
    State getState();
    Cancelable subscribe(StateChangeListener<State> listener);
}

• Cursor responsible for retrieving the state and observing updates.
• Dispatcher responsible for dispatching actions.

That allows you to expose Store functionality as interfaces to your components.

State mapping

Having Cursor interface, it is possible now to have map operation similar to rx.Observable.map(func).
For that purpose new helper class Cursors with map function was introduced.
Usage example:

Store<AppState> store = ...;
Cursor<User> userCursor = Cursors.map(store, state -> state.getUser());
//use mapped cursor in component 
UserPresenter presenter = new UserPresenter(userCursor);

Mapped cursors allow your components to depend only on specific substate they need, instead of depending on the whole state, knowing on how to get to particular substate.

Current implementation of map will only propagate unique values, so it's more efficient to pass mapped Cursor
to upper levels of application.

Other (breaking) changes

• store.forEach(listener) was moved as static function to Cursors.forEach(cursor, listeners);
• action.getValue(index) now returns generic parameter instead of Object.

0.11.1

Replaced @generated annotation with just a comment

0.11.0

Breaking changes

Middleware can be initialized with Store

Now Middleware is split into two functional interfaces.
So if old middleware signature was (store, action, nextDisaptcher) => (),
the new one will be (store, nextDispatcher) => (action) => ().
This middleware structure is much closer to original Redux middleware.

New generated Action Creators (experimental)

If @AutoReducer.Action(generateActionCreators = true),
reductor will generate ActionCreator interface.
The interface will have the same name as reducer with 'Actions' suffix.
Old generated static nested ActionCreator classes in reducer implementations are no longer supported.

As you may use generated action creators directly, explicitly defining action creator interface is recommended.
However generated action creators can be used to prototype your reducer faster,
and then generated interface can be copied to the source code.

Other

Added Generated annotation to all emitted code.

0.10.0

New feature: Action creators

This feature allows defining action creators as interface separately from reducer.
This allows:

• Separate action definition and reducer handler.
• Get rid of direct usage of some of the generated code (action creators generated in AutoReducer reducers).
• Per-action validation for AutoReducer reducers to have the same values as in corresponding action creator.
• Actions can be "shared" between multiple reducers.
• One reducer can handle actions from multiple Action creators.

To create an instance of Action creator Actions.from(class) can be used.
Example: interface,
usage.

"Old" action creators in AutoReducer is deprecated but still supported (will be removed in next version).

Other changes

• Action class now has multiple values (Object[] values instead of Object value).
• New Store method forEach: similar to subscribe but propagate initial value immediately.
• New module reductor-rxjava2 to observe Store as RxJava2 Observable or Flowable.

0.9.3

• Fix reducer code generation for @CombinedState class with no properties

0.9.2

New Features

• Big update on @CombinedState.
  Now @AutoValue value classes are supported as combined state!
  Interfaces as combined state are still supported.

Other improvements

Update code generator for @CombinedState reducers.

• Remove unnecessary state object allocation if all sub-states are the same.
• Use boxed version of sub-state types in reducer, to remove boxing/unboxing when passing to sub-reducers.

0.9.1

• Rename reductor-rx maven artifact to reductor-rxjava
• Updated rxjava version to 1.2.1