For api versioning you make a good point, I am agree with you.
It probably depends how it should be handled. It it has to appear in the URL, with sub-subdomain that ain't readable, fully agree, but, if the version is for example a state of the docs (like for example on date-fns) then I guess "docs" can still be use. Depends of the documentation UX I guess then.
dev.example / testing.example I do that too.
Thanks for your feedback!
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
For api versioning you make a good point, I am agree with you.
It probably depends how it should be handled. It it has to appear in the URL, with sub-subdomain that ain't readable, fully agree, but, if the version is for example a state of the docs (like for example on date-fns) then I guess "docs" can still be use. Depends of the documentation UX I guess then.
dev.example / testing.example I do that too.
Thanks for your feedback!