-
Notifications
You must be signed in to change notification settings - Fork 131
feat: expose events on xscheduler module #870
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
base: dev
Are you sure you want to change the base?
Conversation
|
The latest Buf updates on your PR. Results from workflow Buf Linter / buf (pull_request).
|
a96e5b7 to
ee375bb
Compare
8d3943c to
5093368
Compare
9b9c432 to
ada7012
Compare
5093368 to
c5936b1
Compare
c5936b1 to
c487365
Compare
xmariachi
left a comment
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.
lgtm!
| return err | ||
| } | ||
|
|
||
| oldScheduleKey := getTaskScheduleKey(task) |
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.
Usually we return the struct + err on the keeper's get methods
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.
Oh but the task schedule key can be nil it's not an error, but it's an impossible/forbidden case when we execute a task
| evt, err := cosmostypes.ParseTypedEvent(e) | ||
| require.NoError(t, err) | ||
| parsed = append(parsed, evt) |
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.
maybe consider extracting this for parsing single events, in case we might use it. maybe in a util? just a thought
Purpose of Changes and their Description
Add the emissions of the events below in the
x/schedulermodule:TaskScheduledEvent: Emitted when a task is scheduled or rescheduled at a specific time (i.e. a task can be created without being scheduled, in that case the event is not emitted);TaskUnscheduledEvent: Emitted when a task that was scheduled, is cancelled or unscheduled;TaskExecutedEvent: Emitted when a task is executed.;Are these changes tested and documented?
Unreleasedsection ofCHANGELOG.md?