This repository was archived by the owner on Feb 26, 2024. It is now read-only.
ES6 modules DI proposal #25
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
!This is not meant to be submitted as it is of now!
Annotations
Eventually all the
.$x
properties might become annotations.Provider types (factory/service/value/etc)
There is an issue - annotating non-function values (eg. objects or strings) is tricky. The annotation would have to wrap the value object.
I think the DI itself might provide just two types:
class
(currently "service") andfactory
. It would even not require any special annotation - if it is a function, it's a provider of typefactory
, if it's a class (ES6), it's a provider of typeclass
.That would lead into just a single annotation
@provider
.The downside is that developers have to wrap all the current "values" into a function wrapper, to make it a factory.
The benefit is simplification.
Angular specific providers
On the top of the "type" and "factory", Angular can provide higher level APIs, such as "controller", "filter" or "directive".