vitalets/combodate

EVERY MONTH HAVE 31 DAYS?

Opened this issue · 2 comments

Don't you think the problem is important?

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.

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.