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
{{ message }}
This repository has been archived by the owner on Nov 11, 2022. It is now read-only.
I use a pattern where events can either only be fired from classes in the same package (constructor is package-private) or events can only be caught by classes in the same package (handler is package private)
This makes it really easy to reason about the program flow and I catch a lot of bugs with this pattern.
Without handlers is it possible to restrict which classes can catch events?
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I use a pattern where events can either only be fired from classes in the same package (constructor is package-private) or events can only be caught by classes in the same package (handler is package private)
This makes it really easy to reason about the program flow and I catch a lot of bugs with this pattern.
Without handlers is it possible to restrict which classes can catch events?
The text was updated successfully, but these errors were encountered: