Angular Versioning

[gravidThoughts]

Fantastic plugin.

One potentially large flaw.This plugin is not structured to properly support signature changes across Angular versions.

It is not clear what version of Angular is currently being used to create the completion signatures.

The current design of this plugin requires that one be developing against the Angular version that is used to create the completion settings files.

If the plugin gets updated against a newer version of Angular, developers will be required to update their project, not always convenient or possible.

Perhaps the versioning rules being used by Angular dev team would guarantee that signatures for a major version were guaranteed not to break? Then it is easy to envision that this plugin could be released AngularJS1,2, AngularJS1.3 etc.

Regardless, in my opinion, the versioning story is one of the larger ambiguities related to the use of this plugin, and probably needs to be addressed in the future.

Thanks!

[subhaze]

This is is something I've wanted to address, having the ability to choose which version of angular to use. As it stands currently, it's 1.2