Fix routing behavior when getStaticPaths params include hyphens #7694
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.
Changes
getStaticPaths
implementation includes a keyed objectRouteManifest
, the generatedroute.pattern
doesn't always match the generated routes due to hyphenization.route.pattern
logic to account for hyphens, the correct fix is to update ourgetStaticPaths.keyed
implementation to only store the final, generated pathname of the route. This removes any mismatchedkeys <=> data
relationship. Hyphens are no longer relevant!/route/[a]-[b]
Testing
Test added, existing tests should pass
Docs
Bug fix only