API Deprecated ScheduledTask and subclasses #1195
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.
These classes put configuration concerns in the inheritance hierarchy, making them very inflexible. For example, if the author of some task decides that "yearly" is an adequate frequency, you can't change that in your own project setup. The only advantage those classes have is the fact that you can set up one cron rule for all tasks, but in practice that saves little to no configuration effort.
Base CliController or BuildTask instead, with custom cron job intervals.