-
Notifications
You must be signed in to change notification settings - Fork 25.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bad exports naming for Directive/Component #2356
Comments
@alexeagle we need to discuss how to prioritize this relative to other customer-facing issues -- might need to slip to alpha-30. |
The workaround is in |
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
the top-level 'angular2/angular2' module re-exports Component as ComponentAnnotation. The actual Component class extends Directive. However, we re-export class Directive as DirectiveAnnotation, and the re-exported Directive is just a var declaration. This breaks the angular2.d.ts since it ends up with a Component extends Directive type, where Directive is not a class.
Current workaround is to export the Directive annotation into the .d.ts, but this breaks the application because only decorators should be exposed to JS application.
The text was updated successfully, but these errors were encountered: