coreui / coreui-pro / 37782674203

96%

main: 94%

push

github

feat(MultiSelect): take the validation state from options and events, not from attributes (#1590)

* feat(MultiSelect): take the validation state from options and events, not from attributes

MultiSelect followed the class, aria-invalid and aria-describedby a page wrote
on its select with a MutationObserver, and the form plugin and the stepper marked
the hidden select and the search input as well. The control now resolves one
state and draws it on the frame and on the element that takes the focus.

- The state comes from validationState (invalid and valid stay as aliases), a
  state class on the select at load, a validation that reports the select
  invalid, and :user-invalid / :user-valid under data-coreui-validate.
- A given state is cleared by the next change of the selection; setConfig with
  validation options only updates the state without rebuilding the control.
- A given 'invalid' blocks the submit through setCustomValidity on the select,
  with the text of the linked message or a generic one. A validity the page set
  on the select itself is left alone.
- The form plugin and the stepper leave the select and the search input to the
  component, so the search box no longer turns green under
  data-coreui-validate="valid".
- A native form reset restores the selection and the search the control
  started with and clears its state.

The form validation util gains getValidationState, getUserValidity,
followUserValidity, ownValidationState, setStateValidity and getFeedbackText
for the components that carry their value in a control they draw over.

* build: raise the JS bundle budgets for the MultiSelect validation state

Measured against v6-dev with gzip -9 on both builds: +0.82 KB coreui.bundle.min.js,
+0.83 KB coreui.esm.min.js, +0.88 KB coreui.min.js, and +1.89 KB on the three
unminified bundles, which keep the JSDoc of the new form validation helpers.
Each ceiling leaves about 0.25 KB of headroom over the bundlewatch reading.

* fix(MultiSelect)... (continued)

7400 of 7975 branches covered (92.79%)

Branch coverage included in aggregate %.

143 of 154 new or added lines in 2 files covered. (92.86%)

12800 of 13100 relevant lines covered (97.71%)

1580.31 hits per line