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
I was thinking there would be a specific setup event and then the job gets scheduled for > 1 year in the future:
/**
* Scheduled tasks to run using a cron-like syntax.
*
* This uses [node-schedule](https://github.com/node-schedule/node-schedule) under the hood. The
* object is similar to the rules section, in that you define a cron-string with the following format:
*
* * * * * * *
* ┬ ┬ ┬ ┬ ┬ ┬
* │ │ │ │ │ |
* │ │ │ │ │ └ day of week (0 - 7) (0 or 7 is Sun)
* │ │ │ │ └───── month (1 - 12)
* │ │ │ └────────── day of month (1 - 31)
* │ │ └─────────────── hour (0 - 23)
* │ └──────────────────── minute (0 - 59)
* └───────────────────────── second (0 - 59, OPTIONAL)
*
* Which would look something like:
*
* "scheduler": {
* "0 0 12 * * ?": "schedule/daily_at_twelve.ts",
* "0 9 * * 1-5": "schedule/weekday_wakeup_email.ts"
* }
*
* in practice. There's a lot of great resources on the net showing the general syntax.
*/
Would be pretty crazy if...
You could schedule peril to lint a source directory + license file and send a PR with the updated dates
The text was updated successfully, but these errors were encountered: