This repository was archived by the owner on Apr 12, 2024. It is now read-only.
This repository was archived by the owner on Apr 12, 2024. It is now read-only.
di: Allow arbitrary objects as identifiers for services #10347
Description
This could help us (start to) break away from the string-only ids for services in 1.x, without waiting for 2.0.
Example declaring an injection point
Foo.$inject = [Storage]; // instead of Foo.$inject = ['db'];
function Foo(db) {
...
}Example wiring up the implementation in an angular module:
// These are all meant to be equivalent
angular.module('foo', [])
.value(Storage, new StorageImpl())
.service(Storage, StorageImpl)
.factory(Storage, function() { return new StorageImpl() })
.provider(Storage, function() { this.$get = function() { return new StorageImpl() }; });I am able to implement this in a library where I generate the string IDs for compatibility with Angular 1.3, but it feels pretty hacky and seems like something Angular core should take care of.
For reference, it ends up looking something like this:
Foo.$inject = inject(Storage, Other...);
function Foo(storage, other) {...}
angular.module('foo', [])
.service(id(Storage), StorageImpl);