feat: support Next.js/Nuxt.js-style dynamic route parameters in patterns #44
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds support for Next.js/Nuxt.js-style dynamic route parameters in CODEOWNERS patterns, addressing issue #42.
Modern web frameworks like Next.js and Nuxt.js use square brackets [paramName] in file and directory names to denote dynamic route parameters. This is a fundamental pattern in these frameworks' file-based routing systems.
Examples:
Currently, CODEOWNERS rejects such patterns with an error: