Custom events are being fired twice #4611

Activity

1. ericmdantas commented on Oct 8, 2015

   

   ericmdantas

   on Oct 8, 2015

   ContributorAuthor

   More actions

   For posterity, you should not have outputs: ['someEvent'] and @Output() someEvent:EventEmitter = new EventEmitter().

   Correcting the code in plnkr, we'd have the following:

   import {
     Component, 
     Directive, 
     View, 
     Output, 
     bootstrap, 
     EventEmitter
   } from 'angular2/angular2';
   
   @Directive({
     selector: '[something]',
     host: {
       '(input)': 'inputHandler()'
     },
     outputs: ['fired']
   })
   class SomethingDirective {
     /*@Output()*/ fired: EventEmitter = new EventEmitter();
   
     inputHandler() {
       this.fired.next({});
     }
   }
   
   @Component({
     selector: 'hello'
   })
   @View({
     template: `
       <h2>being fired twice - type to see</h2>
       <input type="text" something (fired)="firedHandler()"/>
       <button type="button" (click)="resetCount()">reset count</button>
       <p>count: {{count}}</p>
     `,
     directives: [SomethingDirective]
   })
   class HelloCmp {
     count: number = 0;
   
     firedHandler() {
       this.count++;
     }
   
     resetCount() {
       this.count = 0;
     }
   }
   
   bootstrap(HelloCmp);

   And then it'd count one by one.

   Thanks, @ericmartinezr.

   👍React with 👍3Reacted by Mor Kadosh, raduc and DmitriyIvanko
2. ericmdantas

   closed this as completedon Oct 8, 2015
3. angular-automatic-lock-bot commented on Sep 7, 2019

   

   angular-automatic-lock-botbot

   on Sep 7, 2019

   More actions

   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.}
4. angular-automatic-lock-bot

   locked and limited conversation to collaborators on Sep 7, 2019