| Interface | Description |
|---|---|
| CompositeKnot<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. |
| 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 | |
| Prime<State,Change,Action> |
| Class | Description |
|---|---|
| ActionsBuilder<Change,Action> | |
| CompositeKnotBuilder<State,Change,Action> | |
| CompositeKnotBuilderKt | |
| CompositeKnotKt | |
| Composition<State,Change,Action> | |
| Effect<State,Action> |
Convenience wrapper around State and optional Action.
|
| EventsBuilder<Change> | |
| InterceptBuilder<State,Change,Action> | |
| KnotBuilder<State,Change,Action> | |
| KnotBuilderKt | |
| KnotKt | |
| PrimeBuilder<State,Change,Action> | |
| PrimeBuilderKt | |
| StateBuilder<State> | |
| WatchBuilder<State,Change,Action> |