Skip to content
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

The events property should allow renaming similar to properties #2272

Closed
vsavkin opened this issue Jun 2, 2015 · 1 comment
Closed

The events property should allow renaming similar to properties #2272

vsavkin opened this issue Jun 2, 2015 · 1 comment
Labels
effort2: days refactoring Issue that involves refactoring or code-cleanup
Milestone

Comments

@vsavkin
Copy link
Contributor

vsavkin commented Jun 2, 2015

The following should work:

@Directive({
  events: ['renamedEvent1 : event1', 'event2']  
})
class MyDirective {
  renamedEvent1: EventEmitter = new EventEmitter();
  event2: EventEmiter = new EventEmitter();
}
@vsavkin vsavkin added P2: required refactoring Issue that involves refactoring or code-cleanup effort2: days labels Jun 2, 2015
@vicb vicb self-assigned this Jun 4, 2015
@vicb vicb added this to the M10 milestone Jun 4, 2015
vicb added a commit to vicb/angular that referenced this issue Jun 4, 2015
vicb added a commit to vicb/angular that referenced this issue Jun 4, 2015
@vicb vicb closed this as completed in 29c72ab Jun 8, 2015
@angular-automatic-lock-bot
Copy link

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.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 6, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
effort2: days refactoring Issue that involves refactoring or code-cleanup
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants