Multiple event types not handled (impossible to) about event-emitter

[NtTestAlert]

#596 it's not events array. Its namespace delimiter.

Indeed, but currently it is impossible to react to multiple events, because using multiple @OnEvent on a single method overwrites the decorator metadata.
One would need to either create a separate wrapper method for every event type (which would become unmaintainable with many events or dynamic arrays), or use EventEmitter2 directly (which defeats the purpose of the library).

Instead the decorator metadata could be implemented in a way that handled that gracefully.
nestjs/common contains a helper method, extendArrayMetadata (present since before 7.0.0) that would do it, while there is no decorator version of that method like SetMetadata that's trivial.

Not always will events that we want to handle conform to something that can be solved with wildcards

Posting a PR momentarily.

[Maligosus]

#596 it's not events array. Its namespace delimiter.

[pklaschka]

I generally speaking hate "+1" comments, but quickly wanted to say that this capability would significantly improve my developer experience with this library.

I don't have a strong opinion about multiple OnEvent() vs a single OnEvents() decorator (although I will say that it just took me some time trying to figure out that my intuitive attempt of using multiple OnEvent() decorators wasn't supported, so if that continues to be unsupported, clear documentation about this would be great), but if one of these options gets added to this library, that will make my day (on whatever day it gets released) 😉 (and enable much cleaner code for these kinds of scenarios).

For now, I'm glad to have found at least a working solution (thanks, @NtTestAlert , for sharing that workaround), but I would greatly appreciate not having to explicitly inject the event emitter into my services just for that.

[kamilmysliwiec]

Let's track this here #657