Information about the version on an implemented feature

[christianbumann]

It would be nice to have the information about the version number in which a feature was implemented. Adding an additional attribute in the source code could be an easy option. Reading it from metadata could be the better option, but harder to implement!?

[daveaglick]

The first question that jumps to mind is "what is a feature?" Is it just changes to the API surface? Is it a new alias and all the associated support code? Could it be both? There's also the question of version numbers across both the core libraries and extensions. Does "1.2" mean the same thing everywhere (probably not)?

In either case, I think it would have to be implemented as explicit metadata on something like an attribute. The problem with trying to infer the first version of a feature is that we'd have to parse the current version and all previous versions to figure out where it was introduced.

One relatively easy thing would be to add an optional introducing version property to CakeMethodAlias and CakePropertyAlias. Then the docs could display that information if it exists.

[pascalberger]

I created https://github.com/cake-build/cake/issues/3017 for extending CakeMethodAlias and CakePropertyAlias