-
Notifications
You must be signed in to change notification settings - Fork 218
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[shell-operator] feat/new operator event handling mechanism #735
base: main
Are you sure you want to change the base?
Conversation
Signed-off-by: Pavel Okhlopkov <[email protected]>
Signed-off-by: Pavel Okhlopkov <[email protected]>
…-operator-event-handling-mechanism
Signed-off-by: Pavel Okhlopkov <[email protected]>
Signed-off-by: Pavel Okhlopkov <[email protected]>
} | ||
|
||
infos := hc.ScheduleController.HandleEvent(crontab) | ||
if createTasksFn == nil { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
And why do we check the input parameters only after we have called HandleEvent? If the functions have not been transferred, we do not use the result that we received earlier.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looks like untouched code. this is not my logic.
previously, we have no returned values, just append to slice in closure.
now we have more clear structure with returning tasks values, if we handle it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I just pointed out what the eye caught on, the correction seems to be small.
Overview
Replace functional pattern with return values
What this PR does / why we need it
Special notes for your reviewer