-
Notifications
You must be signed in to change notification settings - Fork 138
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix next rewrites #411
Fix next rewrites #411
Conversation
🦋 Changeset detectedLatest commit: db981ba The changes in this PR will be included in the next version bump. This PR includes changesets to release 4 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, there were a couple questions in your comment but I'm a bit out of the loop and preoccupied at the moment - sorry.
}; | ||
switch (has.type) { | ||
case "header": | ||
params = fromSource(headers[has.key.toLowerCase()] ?? ""); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just a minor nit to save a few lines of code: just return fromSource(...
1ea06ba
to
7d3d468
Compare
Fix #263
This PR fix the uses of named regex in next.config rewrites.
This one #263 (comment) works just fine now