Replies: 2 comments 1 reply
-
I think the best way to implement something like this is if React Router used a tree-matching algorithm. NOTE: The link below is from Remix, but since it uses React Router, it should still apply. |
Beta Was this translation helpful? Give feedback.
1 reply
-
I opened up #11556 as a POC for this feature |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I have a web application that has unconventional segments which used to work on react router 5 with the use of multiple slugs and validators for path matching, however with the new path matching from v6 it got a bit harder to match this controllers.
Here's a few examples:
www.my-site.com/calendar.event1.create
www.my-site.com/calendar.event2.edit
I know I can just change it to use
/
but unfortunately that would be a breaking change that we're trying to avoid, and also this is a very simple example, there are more complex ones that are not easily solvable. I'll be willing to contribute this feature but would love to get some feedback instead of just wasting my time doing something that won't ever get merged.End product would look something like this:
Beta Was this translation helpful? Give feedback.
All reactions