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

show uncaught top-level exceptions #31

Open
errge11ce opened this issue Oct 12, 2015 · 0 comments
Open

show uncaught top-level exceptions #31

errge11ce opened this issue Oct 12, 2015 · 0 comments

Comments

@errge11ce
Copy link

If the developer creates an invalid DOM tree (e.g. table -> tr instead of table -> tbody -> tr), then react js itself will have strange issues. This is unfortunately can only be caught run time and the developer can see them by opening the browser's javascript console. On the other hand if the dev forgets to look into the console, the application just misbehave and will arrive at stranger and stranger states.

It would be nice to catch all top level exceptions and just replace the whole SPA with the message or at least display it at the top (similarly to connection errors in dev mode).

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