Repository navigation
Support for referencing static variables of a class in the static reflector #10332
Description
I'm submitting a ... (check one with "x")
[ ] bug report
[x] feature request
[ ] support request => Please do not submit support request here, instead see https://github.com/angular/angular/blob/master/CONTRIBUTING.md#question
Current behavior
class MyComponent {
static SYMBOL = new OpaqueSymbol(...);
}
@NgModule({
providers: [{provide: MyComponent.SYMBOL, useValue: 123}]
})
class MyModule{}The above reports an error in ngc.
Expected/desired behavior
The above code would resolve the OpaqueSymbol declared in MyComponent.
What is the motivation / use case for changing the behavior?
New recommended style for declaring module specific opaque tokens.
Metadata
Metadata
Assignees
Labels
No labels
Activity
feat(compiler): Added support for references to static fields. (#10334)
angular-automatic-lock-bot commentedon Sep 9, 2019
This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.
Read more about our automatic conversation locking policy.
This action has been performed automatically by a bot.