de.halfbit.knot

Interface CompositeKnot<State,Change,Action>

All Superinterfaces:

Knot<State,Change,Action>

public CompositeKnot<State,Change,Action>
extends Knot<State,Change,Action>

If your interface Knot becomes big and you want to improve its maintainability and extensibility you may consider to decompose it. You start decomposition by grouping related functionality into, in a certain sense, indecomposable pieces called Primes.

Flowchart diagram

interface Prime defines its own Change's, Action's and Reducer for own changes. It's only the State, what is shared between the Primes. In that respect each Prime can be considered to be a separate interface Knot working on a shared State. Once all Primes are defined, they can be composed together and provided though CompositeKnot.compose function to interface CompositeKnot which implements standard interface Knot interface.

See Also:

interface Knot, Flowchart diagram, interface Prime, interface Knot, CompositeKnot.compose, interface CompositeKnot, interface Knot

Method Summary

Modifier and Type	Method and Description
void	compose(Composition<State,Change,Action> composition)

Methods inherited from interface de.halfbit.knot.Knot

getChange, getDisposable, getState

Method Detail

compose

void compose(Composition<State,Change,Action> composition)