fix: guard dynamic segment propagation to prevent static-siblings regression
When a parallel slot has both a static and dynamic subdirectory matching the target path (e.g. @panel/settings and @panel/[id] for /dashboard/settings), the static match should take priority. Without this guard, BTreeMap iteration order causes [id] to be processed before settings, and the dynamic match incorrectly wins. The fix checks if any static sibling at the current directory level directly matches the next target path segment. If so, dynamic segment subdirectories skip dynamic matching, ensuring the static route is used instead.
Showing
Please
register
or
sign in
to comment