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: respect the replace prop if it is defined #8779

Merged
merged 4 commits into from Jun 7, 2022

Conversation

williamsdyyz
Copy link
Contributor

This is a fix for #8777

@remix-cla-bot
Copy link
Contributor

remix-cla-bot bot commented Apr 7, 2022

Hi @williamsdyyz,

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 Apr 7, 2022

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

@williamsdyyz
Copy link
Contributor Author

Not wanting to be needy here, but I submitted this two months ago and....nothing. Not even a comment.

RR6 is causing me major issues due to bugs and breaking changes, it would be appreciated if the RR6 team focused on fixes to stabilize the current functionality before adding even more new features

@timdorr
Copy link
Member

timdorr commented Jun 3, 2022

I requested some reviews for you now.

@brophdawg11
Copy link
Contributor

It looks this has some conflicts with the 6.4.0 work merged into dev - do you mind getting them resolved and then I'll check if we can get this merged for 6.4.0?

@@ -63,4 +63,6 @@
- turansky
- underager
- vijaypushkin
- rtmann
Copy link
Contributor

Choose a reason for hiding this comment

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

^^ I don't think this is intentional - potentially leftover from the merge conflict resolution?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Sorry. It got sorted not added.

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.

None yet

4 participants