IgniteUI / igniteui-webcomponents / 40333724967

100%

push

github

fix(combo): keep the search text when singleSelect is set again (#2523)

- coercedProperty: onChange runs only when the coerced value changes,
  by Lit's notEqual. An object or array that is set again still runs
  it, because it can hold an in-place change. Before, a framework that
  sets each property on each render, such as React, ran each onChange
  on each render
- combo: setting singleSelect or disableFiltering to its current value
  no longer clears the search text and the filter
- highlight: setting searchText or caseSensitive to its current value
  no longer searches again, so the active match stays. Call search()
  after the content changes
- spec: same-value sets for the decorator, the combo and the highlight,
  and a data array set again after an in-place change. The decorator
  spec no longer expects onChange when a value coerces to the stored one
- docs: CHANGELOG, the combo and highlight spec.md, the coding
  guidelines, and the searchText JSDoc and story

Closes #2516

8757 of 8855 branches covered (98.89%)

Branch coverage included in aggregate %.

10 of 10 new or added lines in 2 files covered. (100.0%)

53496 of 53629 relevant lines covered (99.75%)

3698.81 hits per line