You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What is the point of having a 0 based index for the month field? Shouldn't it be the month number that it corresponds with?
<MonthPicker classes={'datePicker'} {...rest} defaultValue={'Month'} // default is 1900 start={1} // default is ASCENDING reverse // default is false value={value} // mandatory onChange={month => onChange(month)} required={true} />
For some reason in the react developer tools I see: <option key='0' value{0} className={null}>1</option>
Then rendered in html : <option value="0">1</option>
The text was updated successfully, but these errors were encountered:
That's a valid reason. I poked around online and found some interesting comments about it likely coming from C function implementation(Link to stack overflow discussion). That's why I was confused. Traditionally I've posted to my server side complete dates, but for some reason another developer used your library and posted the values from the components individually throwing everything a month back, but the days were correct. Thanks for getting back to me. I'll handle it in the javascript Date implementation.
What is the point of having a 0 based index for the month field? Shouldn't it be the month number that it corresponds with?
<MonthPicker classes={'datePicker'} {...rest} defaultValue={'Month'} // default is 1900 start={1} // default is ASCENDING reverse // default is false value={value} // mandatory onChange={month => onChange(month)} required={true} />
For some reason in the react developer tools I see:
<option key='0' value{0} className={null}>1</option>
Then rendered in html :
<option value="0">1</option>
The text was updated successfully, but these errors were encountered: