-
Notifications
You must be signed in to change notification settings - Fork 160
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
Reactor debug option for large state Maps #178
Labels
Comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Perhaps this use case is too niche to make it into the lib, but I wanted to raise the issue for discussion either way.
Using
Reactor({ debug: true });
is great, but i've found that constantly evaluating state to JS can cause perf issues if state gets too big. For instance, if I have a Map with size roughly equal to 10K in state then the console debugging starts causing noticeable perf slowdown (on my system). However the debug feature is excellent, and turning it off means losing some valuable information.Would it be reasonable to implement a second debug mode for the reactor where it would simply print actions as they are dispatched but not evaluate state to JS?
The text was updated successfully, but these errors were encountered: