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

EVERY MONTH HAVE 31 DAYS? #58

Open
tsoftware-org opened this issue Apr 28, 2016 · 2 comments
Open

EVERY MONTH HAVE 31 DAYS? #58

tsoftware-org opened this issue Apr 28, 2016 · 2 comments

Comments

@tsoftware-org
Copy link

Don't you think the problem is important?

@Dwarner123
Copy link

You just have to use the smart days option to have it use the correct amount of days. It does require that both a month and year be filled in.

@d4rkd0s
Copy link

d4rkd0s commented Jul 11, 2017

Can that be the default? I don't see much of a common use case having the need to pick dates that will NEVER occur...?

Having smart days set to false, means by default this package produces dates that will be invalid in most other datetime libraries and days like Feb 31st 2016, can't be translated into unix time.

Since pull requests are sitting for years. I'm just going to have this fix on a fork for a while.

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

3 participants