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

Fix this context when calling multiple event listeners (fixes #2692). #2693

Merged
merged 1 commit into from Sep 4, 2020

Conversation

mgroenhoff
Copy link
Contributor

  • Bugfix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)

Proposed changes

Fixes #2692

Checklist

  • I have read the contribution guidelines
  • For non-bugfix PRs, I have discussed this change on the forum/slack team.
  • I have run grunt to verify the unit tests pass
  • I have added suitable unit tests to cover the new/changed functionality

@jsf-clabot
Copy link

jsf-clabot commented Sep 4, 2020

CLA assistant check
All committers have signed the CLA.

@knolleary
Copy link
Member

Looks good - thanks for this.

@knolleary knolleary merged commit 44b1819 into node-red:master Sep 4, 2020
@mgroenhoff
Copy link
Contributor Author

mgroenhoff commented Sep 4, 2020

Wow, that was quick! I noticed an error in the test which I pushed but it's closed already.

@knolleary
Copy link
Member

Oops. I got a bit merge happy as it looked good. What's the fix on the test?

@mgroenhoff
Copy link
Contributor Author

mgroenhoff commented Sep 4, 2020

It was a missing msg argument in the second event listener. I have corrected it in my fork. You can diff it to see the change.

@knolleary
Copy link
Member

Got it - thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

this context is different between single and multiple input listeners
3 participants