Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Material-UI website redirect v1-5-0.material-ui.com/* to v1.material-ui.com/*
See original GitHub issue- This is not a v0.x issue.
- I have searched the issues of this repository and believe that this is not a duplicate.
Expected Behavior 🤔
Navigating to https://v1-5-0.material-ui.com/* should redirect to v1.material-ui.com/* (e.g. https://v1-5-0.material-ui.com/demos/buttons/ should redirect to https://v1.material-ui.com/demos/buttons/)
Current Behavior 😯
Navigating to v1-5-0.material-ui.com results in a 404 response
Context 🔦
Our internal company documentation links to the old v1-5-0.material-ui.com/* links. Ideally we would just refactor the links to point to the new urls, but all our documentation is versioned by npm package version, and going back through all the old documentation builds to refactor the urls per npm version would be quite a difficult task. Whereas, I can imagine setting up a redirect might not be quite so difficult? What’s in it for Material-UI? It would mean you would make Google happy. Google loves redirects 😉
| Tech | Version |
|---|---|
| Material-UI | v1.5.x |
Issue Analytics
- State:
- Created 4 years ago
- Comments:5 (4 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Sorry @oliviertassinari for dropping the ball on this one. Thanks for helping out here @m2mathew. 🙏
Solved after #16658 and 95cbe4fd6