coreui / coreui-pro / 36686703425

96%

main: 94%

push

github

refactor(DateRangeInput): drop the rangeChange event (#1470)

rangeChange repeated what startDateChange and endDateChange already
report: each end reports its own change, and the instance holds the
other one. Nothing in the library listened to it, the date range picker
never had one, and the component is new in v6, so no released code
depends on it.

- The events section shows a listener on both end events that reads the
  range with getStartDate() and getEndDate().
- The specs that listened to rangeChange listen to the two end events,
  and a new one checks that setRange() assigns both ends before either
  event fires.

6268 of 6823 branches covered (91.87%)

Branch coverage included in aggregate %.

11336 of 11653 relevant lines covered (97.28%)

863.44 hits per line