[1.20.4] Ref: Events structure #87
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request refactors the structure of the com.lambda.event.events files
I also removed all
Eventinterfaces to events that are never triggeredThe following example is based from this file
This way of creating event classes prevent the accidental registration of unused (never posted to TaskFlow) events as seen here
The only edge case where this is allowed is when the super class shares functions or variables for all the inner classes (example)