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

fix(react-router-dom): fix getSearchParamsForLocation in Firefox #10620

Merged

Conversation

smithki
Copy link
Contributor

@smithki smithki commented Jun 16, 2023

See #10618

This implements the fix proposed here: #10618 (comment)

@changeset-bot
Copy link

changeset-bot bot commented Jun 16, 2023

🦋 Changeset detected

Latest commit: b7ed23d

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 4 packages
Name Type
react-router-dom Patch
react-router Patch
react-router-dom-v5-compat Patch
react-router-native Patch

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

@remix-cla-bot
Copy link
Contributor

remix-cla-bot bot commented Jun 16, 2023

Hi @smithki,

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 CLA Signed label will be added to the pull request.

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

@remix-cla-bot
Copy link
Contributor

remix-cla-bot bot commented Jun 16, 2023

Thank you for signing the Contributor License Agreement. Let's get this merged! 🥳

@smithki smithki changed the title Fix TypeError related to 'useSearchParams' in Firefox web extensions Fix TypeError related to useSearchParams() in web extension content scripts in Firefox Jun 16, 2023
Copy link
Contributor

@brophdawg11 brophdawg11 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the PR!

// web extensions. Relevant Bugzilla tickets:
// https://bugzilla.mozilla.org/show_bug.cgi?id=1414602
// https://bugzilla.mozilla.org/show_bug.cgi?id=1023984
defaultSearchParams.forEach((key) => {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Isn't the signature reversed here and key would be the second parameter?

Screenshot 2023-06-21 at 9 59 00 AM

This also tells me we've not got sufficient test coverage over this, so if you're interested in trying to add a test to around this against useSearchParams I'd like to get one added before we merge this. Otherwise I'll try to get some tests wired up when I have a chance.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Isn't the signature reversed here and key would be the second parameter?

🤦‍♂️ Nice catch, I'll push an update.

As for tests, I'm not familiar enough with this source code to feel confident in providing new test coverage, but if you have some direction I can take a stab at it. Otherwise, it may be easier to pass that along to you in the interest of expediency.

@MichaelDeBoey MichaelDeBoey changed the title Fix TypeError related to useSearchParams() in web extension content scripts in Firefox fix(react-router-dom): fix getSearchParamsForLocation in Firefox Jul 11, 2023
packages/react-router-dom/dom.ts Show resolved Hide resolved
@brophdawg11 brophdawg11 dismissed MichaelDeBoey’s stale review July 13, 2023 14:39

Avoiding optional chaining due to bundle size concerns

@brophdawg11 brophdawg11 merged commit aa65dbd into remix-run:dev Jul 13, 2023
@brophdawg11
Copy link
Contributor

Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants