Skip to content

wrong date format exception #1

Description

@garaboncias

Thank you for your work.

Please make optional the strong validation in the constructor.
I mean in the real word wrong date format is happen and you do not have control over it. In this case it would beneficiary just leave that field out from parsing instead of drop everything with a wrong date format exception.
I mean the best would be in such case
ParsedElement.type should be "error" and
ParsedElement.data should be null
but ParsedElement.dataString should be the original value.

if you would like it I could create an MR for it

Activity

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

Metadata

Metadata

Assignees

Labels

bugSomething isn't workingenhancementNew feature or request

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions