- Browser version: Chrome Version 80.0.3987.106
- Operating system: macOS 10.14
When viewing a given API reference on the website, there's an option to view another version:
It allows for a user to pick another version to swap to and see relevant docs, but it's constrained by what existed at the time the currently chosen doc was written. This means that e.g when a user picks v11.x, they won't be able to go back to v13.x:
without first going back to v12.x.
I'd say this is an antipattern, and that we should unilaterally be storing the versions available in the most recently defined major line. If this seems like a good path forward, i'm happy to implement this myself!
When viewing a given API reference on the website, there's an option to view another version:
It allows for a user to pick another version to swap to and see relevant docs, but it's constrained by what existed at the time the currently chosen doc was written. This means that e.g when a user picks v11.x, they won't be able to go back to v13.x:
without first going back to v12.x.
I'd say this is an antipattern, and that we should unilaterally be storing the versions available in the most recently defined major line. If this seems like a good path forward, i'm happy to implement this myself!