4d291bd810
This is a follow-up to https://github.com/vercel/next.js/pull/23588 to update to use a regex lexer to gather the named regex groups instead of attempting to gather them through executing the regex since it can fail to gather the regex groups when they are using specific matching. This also ensures we don't pass the value as a segment when value is defined and it doesn't use a capture group. Additional tests are added to cover these cases and documentation updated to reflect this. Closes: https://github.com/vercel/next.js/issues/23415 ## Bug - [x] Related issues linked using `fixes #number` - [x] Integration tests added ## Documentation / Examples - [x] Make sure the linting passes |
||
---|---|---|
.. | ||
escape-path-delimiters.ts | ||
format-url.ts | ||
get-asset-path-from-route.ts | ||
get-route-from-asset-path.ts | ||
index.ts | ||
is-dynamic.ts | ||
parse-relative-url.ts | ||
path-match.ts | ||
prepare-destination.ts | ||
querystring.ts | ||
resolve-rewrites-noop.ts | ||
resolve-rewrites.ts | ||
route-matcher.ts | ||
route-regex.ts | ||
sorted-routes.ts |