-
-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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(error pages): account for trailingSlash #9126
Conversation
🦋 Changeset detectedLatest commit: cd11000 The changes in this PR will be included in the next version bump. 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 |
c1d086f
to
f33ece1
Compare
!preview 404-trailing-slash |
Snapshots have been released for the following packages:
Publish Log
Build Log
|
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.
😅 Wow, my two favorite issues have joined forces! LGTM.
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.
Can we add a test case? So we are covered for possible regressions
Sure, but I can't get to it until next week. |
@lilnasy can you add the missing test? |
Ah, completely forgot about this one! |
4505ba5
to
8a09350
Compare
Changes
trailingSlash = always
not working #9079Testing
custom-404-server
fixture and test asssr-api-route-custom-404
tested for the same thing.status-code
fixture and test ascustom-404
tested for the same thing. Migrated the build test case unique tostatus-code
.ssr-api-route-custom-404
fixture and test tossr-error-pages
as its scope wasn't limited to api routes.ssr-error-pages
.Docs
Does not affect usage.