Jiachi LiuandGitHub ab14895ada Fix dynamic route not-found boundary matching (#53564) ...

### What & Why

The dynamic not-found boundary didn't work as expected as it was using the `pathname` to match how many levels of the segements should be matched. For dynamic routes this doesn't work, unlike normal page, the unmatched segment can also hit the not found boundary in the same level.

### How

Use `segment` of loader tree nodes to determine if not-found boundary searching is reached to the end instead of using `pathname`. 
> NOTE: For production `/_not-found` case since it's a valid page on production and still has the original tree, so we handle that as a special case to use the not found loader tree (with empty child routes) to render.

Fixes #53344

2023-08-04 16:07:58 +00:00

..

[slug]

…

not-found

Fix dynamic route not-found boundary matching (#53564)

2023-08-04 16:07:58 +00:00

redirect

…

layout.tsx

…