gorhill/cronexpr

Issues

• leading zero are not accepted

  #31 opened 7 years ago by CircleCode
  2

• documentation should state if range + list accepted

  #41 opened 6 years ago by pjebs
  0

• Could the `expression` field of `Expression` structs be readable somehow?

  #39 opened 6 years ago by jameshiew
  0

• doesnt work in parallel usage (multiple goroutines)

  #26 opened 7 years ago by rhaps107
  3

• Hyphenated hours

  #35 opened 7 years ago by sevagh
  6

• Several parse error

  #33 opened 7 years ago by shogochiai
  0

• Day-of-week parse support for MON-SUN (or `1-7`)

  #27 opened 7 years ago by stayclassychicago
  0

• multi-goroutine map write when init first time

  #19 opened 8 years ago by aiquestion
  1

• Wrong calculation on next schedule on cron expression: "*/5 * * * *"

  #25 opened 8 years ago by etsangsplk
  1

• timezone related error on DST on Next()

  #23 opened 8 years ago by cshiong
  5

• the DST change on pull 17 cause some new error

  #24 opened 8 years ago by cshiong
  0

• Previous command

  #14 opened 8 years ago by derekperkins
  1

• Infinite loop on cron expression `*/60 * * * *`

  #16 opened 8 years ago by Till--H
  1

• Unexported fields in `type Expression`

  #15 opened 8 years ago by Illizian
  0

• Return Error Rather than Panic

  #10 opened 9 years ago by briandowns
  2

• Support something like RANDOM_DELAY

  #9 opened 9 years ago by kelcecil
  0

• Why using panic?

  #8 opened 10 years ago by h4ckm03d
  1

• Improve performance where obvious

  #6 opened 11 years ago by gorhill
  3

• Write better Go

  #5 opened 11 years ago by gorhill
  1

• Add a func to validate whether a cron expression is valid

  #3 opened 11 years ago by gorhill
  1

• Support 'LW': last work day of month

  #1 opened 11 years ago by gorhill
  0

• Fix naming convention as per go-nuts feedback

  #4 opened 11 years ago by gorhill
  1

• Add package comment

  #2 opened 11 years ago
  3