New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Dates.now is not now #16
Comments
Thx. I just removed now in 0.9.0 to keep the consistency. |
same problem here |
same problem this is not working as expected |
This is still an issue as the Dates needs to be change to object Dates {
val today: Date
get() = Date()
val tomorrow: Date
get() = setDate(value = 1)
val yesterday: Date
get() = setDate(value = -1)
} |
I found out that this issue is still existing. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Dates.now is expected to be the current time but instead it's the time that the application has started due to it being initialised as a static property. Shouldn't this return a new Date object every time it gets called?
The text was updated successfully, but these errors were encountered: