What
Add a --validate (config-check) mode: load appsettings.json, validate every job (cron expression, timezone, command), print a report, and exit without executing anything.
Why
Lets users catch a bad cron/timezone before deploying as a service. Great for CI too.
Suggested approach
- Reuse the existing startup validation logic.
- On
--validate, run validation, write a human-readable report, and return a non-zero exit code if any job is invalid.
Acceptance criteria
Good for newcomers — comment to claim it.
What
Add a
--validate(config-check) mode: loadappsettings.json, validate every job (cron expression, timezone, command), print a report, and exit without executing anything.Why
Lets users catch a bad cron/timezone before deploying as a service. Great for CI too.
Suggested approach
--validate, run validation, write a human-readable report, and return a non-zero exit code if any job is invalid.Acceptance criteria
--validateexits 0 when all jobs are valid, non-zero otherwiseGood for newcomers — comment to claim it.