We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Some browsers don't support the redux dev tool extensions and so are being flooded by lot of errors.
redux dev tool
Would you be ok if we try to capture the error and print the message only once ?
The text was updated successfully, but these errors were encountered:
That would be great, ideally we'd get something from the debugger's client early on in the connection setup and abort the debugger hookup altogether.
Sorry, something went wrong.
I guess we should be able to detect the problem when doing connection.init.
connection.init
And create a Model composition for the debugger extension in order to store if we have an active connection or not.
Model
One question, is if we failed to init the connection should we re-try it later or no ?
No branches or pull requests
Description
Some browsers don't support the
redux dev tool
extensions and so are being flooded by lot of errors.Would you be ok if we try to capture the error and print the message only once ?
The text was updated successfully, but these errors were encountered: