-
-
Notifications
You must be signed in to change notification settings - Fork 10.6k
Fix: cant start route with @ within Layout Routes (#8699) #8700
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
Hi @theostavrides, 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 [email protected]. Thanks! - The Remix team |
Thank you for signing the Contributor License Agreement. Let's get this merged! 🥳 |
This would also fix remix-run/remix#2012 |
also fix remix-run/remix#846 |
@theostavrides I'd love to merge this. Would you mind resolving the merge conflicts and updating your branch? It's actually simple, we just reorganized our file structure a bit and the updated code is now in |
@chaance Would be happy to. I'll get on it tomorrow |
* docs: Remove misplaced `npm install` I think this line was originally meant to be in the "Install React Router v6" call, but there's already an `npm install` command shown there. * Sign CLA * Update reach.md Co-authored-by: Tim Dorr <[email protected]>
* Add Backwards Compatibility info to v5 Migration Doc * Fix path * Update contributers * Update phrasing * Update docs/upgrading/v5.md Co-authored-by: Tim Dorr <[email protected]>
* Fix some typos in docs * Sign CLA
* fix: highlight code diff for invoice.jsx Highlight the proper line differences * docs: sign the CLA
Fixes bug #8699
When a route is nested within a layout route, it wont render routes starting with an '@' symbol:
Note that the router works correctly when the parent is NOT a layout route (i.e. has a path defined), or is at the root level: