Нема описа

Rob Figueiredo 1e507e218b v3: Merge 'master' and 'v2' to create a v3 branch, and add a go.mod file пре 7 година
.gitignore e0aa2acff9 Initial commit пре 13 година
.travis.yml 67823cd24d Create .travis.yml пре 11 година
LICENSE 4ab9b1f2d8 Add license пре 13 година
README.md 1e507e218b v3: Merge 'master' and 'v2' to create a v3 branch, and add a go.mod file пре 6 година
constantdelay.go f2c3314377 Return an error rather than panicking on invalid cron specs пре 12 година
constantdelay_test.go f2c3314377 Return an error rather than panicking on invalid cron specs пре 12 година
cron.go 1e507e218b v3: Merge 'master' and 'v2' to create a v3 branch, and add a go.mod file пре 6 година
cron_test.go 1e507e218b v3: Merge 'master' and 'v2' to create a v3 branch, and add a go.mod file пре 6 година
doc.go 1e507e218b v3: Merge 'master' and 'v2' to create a v3 branch, and add a go.mod file пре 6 година
go.mod 1e507e218b v3: Merge 'master' and 'v2' to create a v3 branch, and add a go.mod file пре 6 година
parser.go 1e507e218b v3: Merge 'master' and 'v2' to create a v3 branch, and add a go.mod file пре 6 година
parser_test.go 1e507e218b v3: Merge 'master' and 'v2' to create a v3 branch, and add a go.mod file пре 6 година
spec.go 1e507e218b v3: Merge 'master' and 'v2' to create a v3 branch, and add a go.mod file пре 6 година
spec_test.go 1e507e218b v3: Merge 'master' and 'v2' to create a v3 branch, and add a go.mod file пре 6 година

README.md

GoDoc Build Status

cron

Documentation here: https://godoc.org/github.com/robfig/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 (containing various fixes) and the v2 branch (containing a couple new features), with the addition of Go Modules support. It is currently in development.

These are the 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. This behavior is not currently supported in v3.

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.