Skip to content

Add optional support for invalid dates, to allow working with dates as recorded #137

Description

@rlskoeser

Sometimes historical dates written by humans are wrong - e.g. February 29 of a non leap year.

We should think about how to support these kind of dates that are technically invalid according to our calendar systems, as a different kind of ambiguous date with some margin of error. This might be something be a non-default that has to be opted in with a parameter, since supporting it by default could result in unexpected behavior.

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

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions