Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Sink/NoOp entities #6

Open
beylerian opened this issue Jan 10, 2019 · 0 comments
Open

Sink/NoOp entities #6

beylerian opened this issue Jan 10, 2019 · 0 comments
Labels
enhancement New feature or request

Comments

@beylerian
Copy link
Contributor

beylerian commented Jan 10, 2019

It could be useful to have some "no-op" entities that act as loop/sinks in some situations, where we need to define them but have no state mutation.

For example

object SinkState : State

object SinkReducer : Reducer<State> {
    override fun reduce(currentState: State, action: Action): State = SinkState
}

object NoOpReducer : Reducer<State> {
    override fun reduce(currentState: State, action: Action): State = currentState
}
@beylerian beylerian added the question Further information is requested label Jan 10, 2019
@beylerian beylerian changed the title Sink entities Sink/NoOp entities Jan 10, 2019
@beylerian beylerian added enhancement New feature or request and removed question Further information is requested labels Jun 8, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant