Add "Next run" column to recurring tasks index #165
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Thank you @christopher-b, and sorry for the delay! |
rosa
reviewed
Oct 31, 2024
| @@ -1,7 +1,7 @@ | |||
| class MissionControl::Jobs::RecurringTask | |||
| include ActiveModel::Model | |||
|
|
|||
| attr_accessor :id, :job_class_name, :command, :arguments, :schedule, :last_enqueued_at, :queue_name, :priority | |||
| attr_accessor :id, :job_class_name, :command, :arguments, :schedule, :last_enqueued_at, :next_time, :queue_name, :priority | |||
There was a problem hiding this comment.
Hmm. Either I missed something or things have changed since I created this PR 😄
It should be coming from SolidQueue::RecurringTask, but it seems l needed to add ecd58a9 to make that happen.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 change adds a "Next run" column to the Recurring Tasks index page, which indicates when the job will next be enqueued. This is a feature that I got used to when using GoodJob, and I found I missed in Mission Control.
I'd be happy to hear feedback on the idea or the implementation. Thanks!