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
Allow multiple signal names #172
Conversation
CLA is confirmed. I can merge pending approval from @jdanyow |
@EisenbergEffect Still need to add the test and conform to @jdanyow's specs. I'll do that sometime this week. |
@niieani Had any chance to work on the specs? |
Hey @EisenbergEffect, Happy New Year to you and the Aurelia team! |
If you want to work on this, you will need to rebase on master. |
Yes, I know.
|
@niieani let me know if you want a hand with this- we'd much rather merge your PR though! |
@niieani Ping... |
@jdanyow For review. |
@EisenbergEffect that's odd, I had already rebased it into a single commit, did you force-push rewritten history on this repo? Anyway, I can do it again, just a bit of a pain this wasn't merged before that happened. |
I don't think we did anything like that. If you can do it one more time, I'll get it in. |
So this was never done? I'd love to have this kind of functionality at this moment. |
Additional signal names must be passed in as additional parameters in the binding behaviour, like:
binding & signal:'first':'second':'third'
.Fixes #170.
Note: Individual Contributor License Agreement signed.