Skip to content

leap year  #5

Description

@rfrohl

Hi,
fitting for this day we found a bug concerning the leap year.
See the following example:

Timeliness.parse('2012', :format => 'yyyy', :strict => true)
2012-02-29 00:00:00 +0100

Timeliness.parse('2008', :format => 'yyyy', :strict => true)
2008-02-29 00:00:00 +0100

Timeliness.parse('2009', :format => 'yyyy', :strict => true)
nil

Timeliness.parse('2010', :format => 'yyyy', :strict => true)
nil
Timeliness.parse('2011-02', :format => 'yyyy-mm', :strict => true)
nil

Maybe Timeliness could check for this(29.02.) and return something like 28. 02. instead.

Regards,
Robert

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions