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
{{ message }}
This repository was archived by the owner on Apr 12, 2024. It is now read-only.
(oops, I originally intended to open this issue in the dgeni repository. Is it possible to move it there? Otherwise please just delete it here and I will reopen it in the dgeni repository).
especially when learning AngularJS, it's common for a developer to lookup and browse the docs (https://docs.angularjs.org) to get a better feeling about the API in general. What often bothers me here is, that I'm reading about cool features only to discover later, that it's been added only in a very recent version and that I cannot use it right now given the version currently used in my employer's stack. I know that I could just as easily switch to the archived docs of that particular version, but then I would be missing the cool new features ... I personally only switch back to old documentation versions when tackling a bug that I can't understand otherwise.
That's why I think it'd be very useful if you could include the initial version of a feature.
E.g. take a look at the beauty of the jQuery API documentation regarding this aspect:
I'm not sure whether it is feasible automatically through knowledge of previous builds or whether it is a feature that needs to be actively supported by the writers of the documentation (e.g. using certain annotation placeholders that get automatically resolved when a new version is released).
Nevertheless, I'd love to see that in the AngularJS docs :-)