-
Notifications
You must be signed in to change notification settings - Fork 58
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
possible bug with Redux dev tools middleware #939
Comments
I wonder if it could be the same Redux DevTools issue as this extension issue: reduxjs/redux-devtools#1731. They mention using an older version of the extension to work around the issue; would you mind trying that out? Either that, or it could be related to us using a relatively old version of Redux (4.0.5 from react-dart), or other bugs in |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe your issue here... If it is a bug - PLEASE follow our bug submission guidelines.
(Sorry, the link https://github.com/Workiva/over_react/blob/master/.github/CONTRIBUTING.md#bug-reports is broken, and https://github.com/Workiva/over_react/blob/master/CONTRIBUTING.md doesn't say much about bug reports.)
When I load my app using OverReact and Redux, I see this on startup:
and I'm unable to use Redux dev tools (I assume because of the above error):
Here's the full text and stack trace:
This is in this repo on the branch
419-migrate-to-dart-null-safety-mode
, relevant setup code is here:https://github.com/UC-Davis-molecular-computing/scadnano/blob/69d1e09bfff129e01617e3624312599fbfef9453/lib/src/app.dart#L127-L134
Here's that code
I can verify that the print message occurs, so it is setting up
DevToolsStore
(not the normal productionStore
in theelse
clause a few lines later).I imagine I'm just doing something wrong, but I haven't changed this setup code in years and it always worked before. It's also not because I recently upgraded to OverReact 5.3.0; before I starting migrating to null safety a few days ago, I used OverReact 4.0.0 and saw the same error.
I'm just hoping someone has seen this error before and has an idea what might be causing it.
The text was updated successfully, but these errors were encountered: