Rename angular-hint

[SomeKittens]

angular-hint has grown far beyond just providing hints about controller names. The current project scope centers around instrumenting Angular apps so that consumers (primarily Batarang at this point but many more in the future) can process that data.

We should change the name to reflect the new scope. What should we change it to?

[SomeKittens]

ng-decorator

Since a lot of what we're doing here is following the Decorator pattern, why don't we just call it that? (ng-instrumentation as an alternative).

[SomeKittens]

utility-belt

The thing that Batarang depends on!

[SomeKittens]

ng-elf

The programmer's little helper!

[rhaps0dy]

ng-debug[ger]

Boring, but clear and correct.

[Martinspire]

ng-linter

or

angular-linter

Cause technically you are providing support that other linters for popular IDE's are doing. I think you can go even further to see if you follow best practices and add additional error-information and tools to do better debugging (especially on what goes wrong).
And instead of IDE integration, you provide this on the page you have running, so you use this with whatever livereload function you use.

[jimschubert]

ng-sentinel, because it sounds cool.

[rev087]

ng-inspector

Wait...nevermind :p

[rev087]

I think the term most appropriate is something related to instrumentation, which is the feature this module is supposed to provide.

Maybe simply angular-instrumentation? A bit boring, but descriptive.

[jswhisperer]

ng-alchemist because it's magic and science that makes gold.

[doopydook]

I kinda like where @rev087 is going. maybe ng-instrument. And to @SomeKittens point about processing data, maybe ng-process.

Other ideas:
ng-examine
ng-expose
ng-gadget
ng-tool

[rev087]

Too bad Protractor already exists, being the "instrument" to measure "angles"!

[btford]

ng-{{instrumentName}}, where instrumentName is trumpet, trombone, etc.

[rbutera]

@rev087 wait a second.... there it is! "Angles".