[FIXED][3.1] Date.parseDate problem

[mono blaine]

Executing the following line

Date.parseDate('2009-00-12', 'Y-m-d', true)

gives

Dec 12 2009

where it should be just null. That cannot be a feature, right?

[Condor]

You could fix it by using:

"m = m >= -1? m : Ext.num(def.m - 1, dt.getMonth());",

But I'm for changing:

"y = Ext.num(y, Ext.num(def.y, dt.getFullYear()));",
"m = Ext.num(m, Ext.num(def.m - 1, dt.getMonth()));",
"d = Ext.num(d, Ext.num(def.d, dt.getDate()));",
"h = Ext.num(h, Ext.num(def.h, dt.getHours()));",
"i = Ext.num(i, Ext.num(def.i, dt.getMinutes()));",
"s = Ext.num(s, Ext.num(def.s, dt.getSeconds()));",
"ms = Ext.num(ms, Ext.num(def.ms, dt.getMilliseconds()));",

[mono blaine]

Thanks!

[mystix]

@condor, would it be easier to just check for this particular edge case (the only one i can see actually -- correct me if i'm wrong) instead?


}else if(strict === true && (m < 0 || !Date.isValid(y, m + 1, d, h, i, s, ms))){

we really only need to check the month value in this case because of the addition we're performing on it before passing it to Date.isValid() for further checks.



on 2nd thought, i'd go for @condor's suggestion of switching the checks to use Ext.num() all the way
-- it's simply more foolproof.

[hendricd]

Condor's recommendation is now in SVN-5819.
Thus:

Date.parseDate('2009-00-12', 'Y-m-d', true);

now yields the expected 'null'

@Mystix -- can you throw some more 'twisted' tests at it?