don't accept inexact numbers while parsing date values, closes #180

[OlegYch]

Pull Request Checklist

• Have you read through the contributor guidelines?
• Have you signed the Typesafe CLA?
• Have you squashed your commits?
• Have you added copyright headers to new files?
• Have you updated the documentation?
• Have you added tests for any changed functionality?

Fixes

Fixes #180

Purpose

Rejects inexact numbers as input for date parsers, they are limited to Long anyway

Background Context

BigDecimal.toLong takes inappropriate amount of time for something like 1000000000e1000000000

[dwijnand]

LGTM! Thank you.

[OlegYch]

@dwijnand should i submit this against 2.6 branch too?

[dwijnand]

I'm not sure, but I would think we probably want this fixed in 2.6 too. Whether or not that means a second PR.. I also don't know. 🙂

[marcospereira]

Hi @OlegYch and @dwijnand,

Yes, we probably want to backport this to 2.6.x, but you won't need a new PR. We can cherry-pick on our side.

[marcospereira]

Looks good to me, thank you so much @OlegYch. I think we can have comprehensive tests for this fix. I'm also in doubt of a small change (see question).

Besides that, LGTM.

Best

[marcospereira]

LGTM, thank you @OlegYch.