-
Notifications
You must be signed in to change notification settings - Fork 94
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
Using Redux Observable to handle async leads to actions being fired twice #67
Comments
Hey @walleXD That's probably happening because your async action fires both on the renderer and the main thread. Have you tried aliased actions ? |
I am just firing the actions in the renderer. Should I scope them with Aliased actions allow us to fire the action in the main thread but this happens in the renderer but I didn’t try to use aliased action On the main thread with redux-observable. Will report back in my findings. |
Yeah, so depending on what you're doing, your option is to either use the |
Hey,
I was trying to use
redux-observable
but thesynchronous
action which is fired by theasync
action gets fired twice.For example, once I run
increment_async
action, which fires theincrement
action after 1000ms, theincrement
action is being fire twice. This only happens after setting upelectron-redux
Any idea why that would be happening?
Thanks a bunch 🙏🏼
The text was updated successfully, but these errors were encountered: