| Interface | Description |
|---|---|
| CompositeKnot<State> |
If your
interface Knot becomes big and you want to improve its redability and maintainability, you may consider
to decompose it. You start decomposition by grouping related functionality into, in a certain sense,
indecomposable pieces called Primes. |
| Knot<State,Change> |
Knot helps managing application state by reacting on events and performing asynchronous
actions in a structured way. There are five core concepts Knot defines: State, Change,
Reducer,
class Effect and Action. |
| KnotDsl | |
| Store<State> |
Store is a disposable container for a State.
|
| TestCompositeKnot<State,Change> |
| Class | Description |
|---|---|
| ActionsBuilder<Change,Action> |
A configuration builder for Action related declarations.
|
| CompositeKnotBuilder<State> |
A configuration builder for a
interface CompositeKnot. |
| CompositeKnotBuilderKt | |
| Effect<State,Action> |
Convenience wrapper around State and optional Action.
|
| EventsBuilder<Change> |
A configuration builder for
Events related declarations. |
| KnotBuilder<State,Change,Action> |
A configuration builder for a
interface Knot. |
| KnotBuilderKt | |
| KnotKt | |
| PrimeBuilder<State,Change,Action> |
A configuration builder for a
Prime. |
| StateBuilder<State> |
A configuration builder for State related declarations.
|