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
Currently the event(s) triggered the controller execution is accessible from the Conext object. There is already a consensus that using these events is an antipattern in operators. Controller Runtime does not expose these event either.
Removing them will have two benefits:
The intended usage is more obvious, so we won't even allow users to use events, so the mentioned anti-patter is not even possible to implement
We can simplify the DefaultEventHandler so we don't store events, just a flag is the controller should be executed or not. This will reduce memory consumption.
Side effects:
The framework will be more opinionated (in this situation is not necessarily a bad thing).
The text was updated successfully, but these errors were encountered:
Currently the event(s) triggered the controller execution is accessible from the Conext object. There is already a consensus that using these events is an antipattern in operators. Controller Runtime does not expose these event either.
Removing them will have two benefits:
Side effects:
The text was updated successfully, but these errors were encountered: