coreui / coreui-pro / 37136676852

96%

main: 94%

push

github

fix(DateInput): keep the shown value on setConfig without a date (#1536)

* fix(DateInput): keep the shown value on setConfig without a date

setConfig() rebuilt the sections from the configured date, which is the
one the field was created with. A field the user had typed into went
back to that date, or to empty, on any setConfig() call that did not
pass a date, such as new limits or a new locale, and fired dateChange
with the old value or null.

setConfig() now rebuilds from the date the field shows, and an explicit
date still replaces it. A date typed under limits that rejected it is
taken once new limits accept it. reset() keeps returning to the date the
field was created with. TimeInput shares the fix.

* fix(DateInput): keep a partly typed date when setConfig keeps the sections

Without a date, setConfig() keeps the sections as they are when the new
options give the same sections, so a partly typed date survives new
limits. When the sections change, the field is rebuilt from the date it
shows, as before. Specs cover the dateChange fired when new limits accept
a typed date, reset() after such a call, and a date with more precision
than the sections show, which is no longer brought back by a later
format.

* chore: raise the coreui.bundle.js, coreui.esm.js and coreui.esm.min.js budgets

setConfig() keeping the sections adds 72 B to coreui.bundle.js, 74 B to
coreui.esm.js and 71 B to coreui.esm.min.js (gzip -9, against v6-dev).
The first two went over their ceilings and the third was left with about
10 B, so each goes up by 0.25 kB.

6782 of 7335 branches covered (92.46%)

Branch coverage included in aggregate %.

5 of 5 new or added lines in 1 file covered. (100.0%)

11933 of 12226 relevant lines covered (97.6%)

1487.27 hits per line