Version Number
N/A (Documentation / Hosting Issue)
Codesandbox/Expo snack
https://react-hook-form.com vs https://www.react-hook-form.com
Description
There is a deployment/DNS misconfiguration causing the www subdomain to serve a legacy, frozen-in-time version of the documentation, while the apex domain serves the modern, up-to-date documentation.
Steps to reproduce
- Go to the apex domain:
https://react-hook-form.com/docs/useform/seterror/
- Observation: Shows modern V7+ docs.
setError type is documented as ErrorOption, and there are more cards in the API section at https://react-hook-form.com/docs/.
- Go to the
www subdomain: https://www.react-hook-form.com/api/useform/seterror/
- Observation: Shows outdated, legacy docs.
setError type is documented strictly as FieldError, and there are fewer API cards at https://www.react-hook-form.com/api/.
Expected behaviour
Traffic to www.react-hook-form.com should permanently redirect (301) to the apex domain react-hook-form.com so developers aren't accidentally served outdated API types and legacy documentation.
What browsers are you seeing the problem on?
Firefox
Relevant log output
Code of Conduct
Version Number
N/A (Documentation / Hosting Issue)
Codesandbox/Expo snack
https://react-hook-form.com vs https://www.react-hook-form.com
Description
There is a deployment/DNS misconfiguration causing the
wwwsubdomain to serve a legacy, frozen-in-time version of the documentation, while the apex domain serves the modern, up-to-date documentation.Steps to reproduce
https://react-hook-form.com/docs/useform/seterror/setErrortype is documented asErrorOption, and there are more cards in the API section athttps://react-hook-form.com/docs/.wwwsubdomain:https://www.react-hook-form.com/api/useform/seterror/setErrortype is documented strictly asFieldError, and there are fewer API cards athttps://www.react-hook-form.com/api/.Expected behaviour
Traffic to
www.react-hook-form.comshould permanently redirect (301) to the apex domainreact-hook-form.comso developers aren't accidentally served outdated API types and legacy documentation.What browsers are you seeing the problem on?
Firefox
Relevant log output
Code of Conduct