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
For cross-cutting concerns like logging and debugging, it would be convenient to support registering listeners by category (or tag or whatever) alone, without limiting by type.
This will require a) registering the handler for all known types on the target and b) watching all future listener registrations on the target for new types.
This will have the very obvious limitation that it will be entirely unable to intercept event types not otherwise being listened for by Eventi. Thus, we should never allow/imply support for an entirely empty listener definition (i.e. a "catch-all" listener).
The text was updated successfully, but these errors were encountered:
For cross-cutting concerns like logging and debugging, it would be convenient to support registering listeners by category (or tag or whatever) alone, without limiting by type.
This will require a) registering the handler for all known types on the target and b) watching all future listener registrations on the target for new types.
This will have the very obvious limitation that it will be entirely unable to intercept event types not otherwise being listened for by Eventi. Thus, we should never allow/imply support for an entirely empty listener definition (i.e. a "catch-all" listener).
The text was updated successfully, but these errors were encountered: