Open HonkingGoose opened 3 years ago
I see. We need to wrap the App component with react-error-boundary, and then 1) give the user the option to reset the comparator and 2) send the error caught to Sentry.
That react-error-boundary
tool seems nice!
Describe the bug
Error message bubbling up to browser console log.
Give the steps to reproduce
The idea here is basically that a user is making a query string by hand to get around the pre-fetched versions in the comparator interface.
Steps to reproduce:
v.1.0.0
is not a valid version, it should bev1.0.0
of course.TypeError: Invalid Version: v.1.0.0
What browsers are you seeing the problem on?
Firefox
Have you thought of a possible solution?
Yes
If you have thought of a solution, please tell us about it!
I think we need to wrap the relevant code in a try/catch block, and capture this kind of bad input, and prevent it from bubbling up to the browser window console log.
Do you want to help fix the bug?
No
Is there anything else we need to know?
No response