No Description

Rob Figueiredo 605d51319c spec_test.go: fix tests when run in UTC as local time zone 6 years ago
.gitignore e0aa2acff9 Initial commit 13 years ago
.travis.yml 67823cd24d Create .travis.yml 11 years ago
LICENSE 4ab9b1f2d8 Add license 13 years ago
README.md 4813ba2496 Recommend CRON_TZ=(Location) to specify the time zone of a schedule. 6 years ago
constantdelay.go f2c3314377 Return an error rather than panicking on invalid cron specs 12 years ago
constantdelay_test.go f2c3314377 Return an error rather than panicking on invalid cron specs 12 years ago
cron.go 1f8ec97c87 Functional options, Optional seconds, Overridable parser 6 years ago
cron_test.go d10bec7141 gofmt 6 years ago
doc.go 4813ba2496 Recommend CRON_TZ=(Location) to specify the time zone of a schedule. 6 years ago
go.mod 605d51319c spec_test.go: fix tests when run in UTC as local time zone 6 years ago
option.go 1f8ec97c87 Functional options, Optional seconds, Overridable parser 6 years ago
option_test.go 1f8ec97c87 Functional options, Optional seconds, Overridable parser 6 years ago
parser.go 4813ba2496 Recommend CRON_TZ=(Location) to specify the time zone of a schedule. 6 years ago
parser_test.go 4813ba2496 Recommend CRON_TZ=(Location) to specify the time zone of a schedule. 6 years ago
spec.go dbf3220455 spec.go: adjust times when rolling the clock forward to handle non-existent midnight 6 years ago
spec_test.go 605d51319c spec_test.go: fix tests when run in UTC as local time zone 6 years ago

README.md

GoDoc Build Status

cron

DRAFT - Upgrading to v3

cron v3 is a major upgrade to the library that addresses all outstanding bugs, feature requests, and clarifications around usage. It is based on a merge of master which contains various fixes to issues found over the years and the v2 branch which contains some backwards-incompatible features like removing cron jobs. In addition, it adds support for Go Modules and cleans up rough edges like the timezone support.

It is in development and will be considered released once a 3.0 version is tagged. It is backwards incompatible with both the v1 and v2 branches.

Updates required:

  • The v1 branch accepted an optional seconds field at the beginning of the cron spec. This is non-standard and has led to a lot of confusion. The new default parser conforms to the standard as described by the Cron wikipedia page.

UPDATING: To retain the old behavior, construct your Cron with a custom parser:

  cron.New(
      cron.WithParser(
          cron.SecondOptional | cron.Hour | cron.Dom | cron.Month | cron.Dow | cron.Descriptor))
  • The Cron type now accepts functional options on construction rather than the ad-hoc behavior modification mechanisms before (setting a field, calling a setter).

UPDATING: Code that sets Cron.ErrorLogger or calls Cron.SetLocation must be updated to provide those values on construction.

  • CRON_TZ is now the recommended way to specify the timezone of a single schedule, which is sanctioned by the specification. The legacy "TZ=" prefix will continue to be supported since it is unambiguous and easy to do so.

Background - Cron spec format

There are two cron spec formats in common usage:

The original version of this package included an optional "seconds" field, which made it incompatible with both of these formats. Instead, the schedule parser has been extended to support both types.