Skip to content

Conversation

@BlankSergey
Copy link

@BlankSergey BlankSergey commented Nov 21, 2019

Because it is UI tests sometimes failed with incorrect date
For exapmle: now 2019-11-21
birthday(23, 65) returns 1996-11-26
It is wrong because for birthday 1996-11-26 it is 22 years old now. Not 23

…etimes failed with incorrect date

Add to birthday() currentMonth and currentDay because it is tests sometimes failed with incorrect date

Fix test coverage
@BlankSergey
Copy link
Author

@jmattsson , can you help, please?
CI is unstbale (it was success before).
And coverage magic decreased

@jmattsson
Copy link
Member

@BlankSergey Nope, I know nothing about this repo. Never touched it in my life, sorry. You probably meant to tag someone else :)

@beniregev
Copy link

Why not use Java 8 Time API? All dates will be related to UTC and calculations will be correct. For example: in UTC (a.k.a. GMT) it's 2019-11-25 16:00 and in Hong-Kong it's 2019-11-26 01:00AM. Using Java 8 Time API will give us the correct result for both locations, both timezones, without any effort.

@BlankSergey
Copy link
Author

BlankSergey commented Nov 26, 2019

@BlankSergey Nope, I know nothing about this repo. Never touched it in my life, sorry. You probably meant to tag someone else :)

I'm sorry :)

@BlankSergey
Copy link
Author

Why not use Java 8 Time API? All dates will be related to UTC and calculations will be correct. For example: in UTC (a.k.a. GMT) it's 2019-11-25 16:00 and in Hong-Kong it's 2019-11-26 01:00AM. Using Java 8 Time API will give us the correct result for both locations, both timezones, without any effort.

In CONTRIBUTING.md writes:

Need to maintain compatibility with Java 1.6 (and Android). Therefore any attempt to migrate to 1.6

JDKs and above will not be merged back in.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants