Nested fs routes not matched

[garth]

Given the following file routes:

item.$id.edit.tsx
item.$id.tsx

when navigating to /item/1/edit the item.$id.tsx route is matched.

To me this looks like a bug since in the route component the value of params.id is returned as 1 not 1.edit (as the matched path might suggest) but maybe it's intentional?

Is there a way to tell react router which route to prioritise when matching?

[garth]

I have added a failing test for the above to the react-router-fs-routes package:

main...garth:react-router:main

[garth]

After a bit more digging, it seems that RR is treating these as nested routes, so a workaround is to add a hidden suffix to the "parent".... eg item.$id._whatever.tsx.