[docs] Force /base-ui redirect
#45083
Open
+17
−55
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Netlify deploy preview
Bundle size reportBundle size will be reported once CircleCI build #789286 finishes. |
|
https://deploy-preview-45083--material-ui.netlify.app/base-ui/ |
|
The redirect appears to be correct in the netlify deploy log: https://app.netlify.com/sites/material-ui/deploys/67909b10db98830008a44b56#L1449 |
mj12albert
force-pushed
the
docs/301-mui-base
branch
from
477c918 to
025df7d
Compare
|
Turns out https://docs.netlify.com/routing/redirects/rewrites-proxies/#shadowing |
mj12albert
changed the title
/base-ui redirect
There was a problem hiding this comment.
As @alexfauquette suggested somewhere else, I think it's better to remove the page instead of using !
mj12albert
force-pushed
the
docs/301-mui-base
branch
from
1851abb to
17f1a6e
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Deleted the corresponding page to make the redirect work, also added a redirect in the Next.js config (for client side routing)