This is an informational request. For Tukio v2, I am trying to clean up some legacy design. One of the things that I don't think I thought through very well is that attribute-based registration supports specifying multiple attributes on the same listener. I... don't really see how that's useful. If anything, it's just making the logic for addListener() more complicated and confusing. Like, if there are attributes defined and a priority is passed to addListener(), what happens? What overrides what?
So I want to remove it.
Before I do so, does anyone rely on that functionality, and is not able to get the same behavior another way? I really cannot think of a use case, but if you can, please share. If no one has any, I will most likely remove that ability to make the code simpler.
This is an informational request. For Tukio v2, I am trying to clean up some legacy design. One of the things that I don't think I thought through very well is that attribute-based registration supports specifying multiple attributes on the same listener. I... don't really see how that's useful. If anything, it's just making the logic for
addListener()more complicated and confusing. Like, if there are attributes defined and a priority is passed toaddListener(), what happens? What overrides what?So I want to remove it.
Before I do so, does anyone rely on that functionality, and is not able to get the same behavior another way? I really cannot think of a use case, but if you can, please share. If no one has any, I will most likely remove that ability to make the code simpler.