-
- Notifications
You must be signed in to change notification settings - Fork 10.7k
fix(react-router): don't throw if the url hash is not a valid URI component #13247
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
Conversation
🦋 Changeset detectedLatest commit: 6551f5d The changes in this PR will be included in the next version bump. This PR includes changesets to release 11 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
Hi @vezaynk, Welcome, and thank you for contributing to React Router! Before we consider your pull request, we ask that you sign our Contributor License Agreement (CLA). We require this only once. You may review the CLA and sign it by adding your name to contributors.yml. Once the CLA is signed, the If you have already signed the CLA and received this response in error, or if you have any questions, please contact us at hello@remix.run. Thanks! - The Remix team |
Thank you for signing the Contributor License Agreement. Let's get this merged! 🥳 |
This needs to be based against the |
@timdorr Done! |
@timdorr Could this get a ✅? This fixes a real bug for my team. |
@timdorr Does this PR need anything else to be merged? It looks like merging is restricted to members only. 😁 |
Just a review by a core team member, as per our governance policy: https://github.com/remix-run/react-router/blob/main/GOVERNANCE.md#bugissue-process |
Could you add a changeset? |
@brophdawg11 Done! |
🤖 Hello there, We just published version Thanks! |
🤖 Hello there, We just published version Thanks! |
Some tooling might pass arbitrary strings in the
window.location.hash
. React Router should not crash if the value is not decodable.In our case, for example, a user interacted with a URL that Datadog injected some tracking info into and the call turned to:
...which crashed the view with the following error:
To avoid this in the future, I would like to suggest that a failure to decode the portion of the URL be preventing from throwing, by wrapping in a
try-catch
.