Validate that no static redirect routes are declared after dynamic ones #26307
+21
−1
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.
Validate that no static redirect routes are present in
public/__redirectsafter any dynamic rule has been declared to avoid over shadowingSummary
The order of application of redirect rules matters. From the documentation:
https://developers.cloudflare.com/pages/configuration/redirects/#per-file:
This change helps to enforce these points.
Output on issue
When a static route is found after any dynamic route has been declared the output is similar to the following:
and the
bin/validate-redirects.tswill return a non-zero (error) codeDocumentation checklist
This adds an additional validation to the rules listed in public/__redirects that should be triggered ahead of merging