You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A regular workflow that I have when I don't remember something in date-fns is searching it in google and clicking on the result that takes me to the oficial documentation. The problem is that those results, in almost all cases, take me to the old version of the library and I ended up using deprecated methods.
I'll give an example.
I search for date fns format and i get this result:
I click the result and I arrive at the documentation without any warning or sign that I'm looking at a old version (1.30 in this case)
Some people will start reading this and will get unexpected errors and will get frustrated by not getting something working even thou the are taking it directly from the documentation.
Proposed solution
I guess there are two options here.
Show a BIG message indicating that they are arriving at legacy docs page and they should check the version that they are using and move to that version instead.
Make a redirect to the latest version as soon as they arrived at the docs.
I like the first option the better because is less intrusive and also the second option could damage the SEO (not sure about it)
Either way, I would like to contribute with a PR once a decision has been made.
Thanks!
The text was updated successfully, but these errors were encountered:
Hi everybody! thank you for the great work.
A regular workflow that I have when I don't remember something in date-fns is searching it in google and clicking on the result that takes me to the oficial documentation. The problem is that those results, in almost all cases, take me to the old version of the library and I ended up using deprecated methods.
I'll give an example.
I search for
date fns format
and i get this result:I click the result and I arrive at the documentation without any warning or sign that I'm looking at a old version (1.30 in this case)
Some people will start reading this and will get unexpected errors and will get frustrated by not getting something working even thou the are taking it directly from the documentation.
Proposed solution
I guess there are two options here.
Show a BIG message indicating that they are arriving at legacy docs page and they should check the version that they are using and move to that version instead.
Make a redirect to the latest version as soon as they arrived at the docs.
I like the first option the better because is less intrusive and also the second option could damage the SEO (not sure about it)
Either way, I would like to contribute with a PR once a decision has been made.
Thanks!
The text was updated successfully, but these errors were encountered: