Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Sugar (*) syntax does not support @Output (and exportAs) #12121

@shlomiassaf

Description

@shlomiassaf

I'm submitting a ... (check one with "x")

[ x] bug report => search github for a similar issue or PR before submitting
[ ] 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
When using sugar syntax I couldn't find a way to register to @Outputs.
The expression does not handle (output) and it's not possible to put the output on the element itself since that element is not the actual directive.
I would also like to point out that exportAs is not supported in * directives.

Expected behavior
Allow to register to events on the directive.

What is the motivation / use case for changing the behavior?
Sugared directives should be on par with regular directives (@Output, exportAs) as it might cause confusion.
At least support parsing output's on the expression.

  • Angular version: 2.0.1

Metadata

Metadata

Assignees

No one assigned

    Labels

    P4A relatively minor issue that is not relevant to core functionsarea: coreIssues related to the framework runtimecore: ng-template and *microsyntaxfeatureIssue that requests a new featurefeature: under considerationFeature request for which voting has completed and the request is now under considerationfreq1: low

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions