Skip to content
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

Closed
erwinknoop opened this issue Mar 1, 2017 · 5 comments
Closed

Dates.now is not now #16

erwinknoop opened this issue Mar 1, 2017 · 5 comments

Comments

@erwinknoop
Copy link

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?

@hotchemi
Copy link
Owner

Thx. I just removed now in 0.9.0 to keep the consistency.
Please use today.

@antonioreyna
Copy link

same problem here

@ericpearson
Copy link

same problem this is not working as expected

@lilHermit
Copy link

This is still an issue as the val is set on first use

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)
}

@shawn-gosam
Copy link

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
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants