$FilterProvider.register() accept object in addition to name/factory arguments

[sgoll]

Right now, both $ControllerProvider.register and $CompileProvider.directive, in addition to the usual pair of name and factory/constructor arguments, accept an object as a single argument, mapping names to factory/constructor functions.

This makes it possible to initialize a bunch of controllers and directives at once, e.g. from the exports of an AMD module, by calling app.directive(require('directives')).controller(require('controllers')).

This is not possible however with $FilterProvider.register which has no special code for parsing objects – which could be as simple as forEach(name, reverseParams(register)) as in $CompileProvider.directive.

I'd like to know if there is a special reason for this and, if not, whether I should create a pull request for the proposed change.

[petebacondarwin]

This is a good idea. Feel free to send in a PR.
You'll need to look here: https://github.com/angular/angular.js/blob/master/src/ng/filter.js#L81-L83
Don't forget that you must sign the CLA, include unit tests and make sure your commit messages are correctly formatted.
Thanks