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

Use of reducers on messages? #7

Open
jellea opened this issue Dec 27, 2015 · 0 comments
Open

Use of reducers on messages? #7

jellea opened this issue Dec 27, 2015 · 0 comments

Comments

@jellea
Copy link

jellea commented Dec 27, 2015

If I understand it correctly Messages are thrown away when they come from the channel and are directly being processed/mutated on to the app atom. Would it be interesting to take a more reactive approach here: keeping the messages instead and reduce over the messages to get the current state like in Elm? This gives a more flexible/reproducible history and allows you to for instance hot swap the processing protocols and see history change with it (like in the time travelling debugger). Planning to give it a try myself in the next coming days, but would love to have your ideas/opinion upfront.

@jellea jellea mentioned this issue Jan 10, 2016
4 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant