You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be quite neat to allow for multiple event listeners per node even if they're of the same type. It already works when one is using a modifier and the other doesn't, but otherwise there will be an error about Attributes need to be unique. I've already looked into the code and it could be changed by moving the check for unique attributes a few lines lower and giving it an extra case for EventHandlers. Tests are still green after the change.
Sure, but I don't see much reason against supporting the notation I proposed especially given it already works with different modifiers. It currently seems to be more of an accidental restriction of the unique attributes check. Having the ability to attach multiple handlers is imho more in line with using multiple addEventListeners and seems easier to change, as the functions are not arbitrarily entangled.
It would be quite neat to allow for multiple event listeners per node even if they're of the same type. It already works when one is using a modifier and the other doesn't, but otherwise there will be an error about
Attributes need to be unique
. I've already looked into the code and it could be changed by moving the check for unique attributes a few lines lower and giving it an extra case for EventHandlers. Tests are still green after the change.The text was updated successfully, but these errors were encountered: