• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

coreui / coreui-pro / 37842834951
96%
main: 94%

Build:
Build:
LAST BUILD BRANCH: v6-dev
DEFAULT BRANCH: main
Ran 08 Oct 2026 08:55PM UTC
Jobs 1
Files 82
Run time 1min
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

08 Oct 2026 08:53PM UTC coverage: 95.925% (+0.04%) from 95.889%
37842834951

push

github

web-flow
feat(ChipInput): carry the chips in a validated field and take a validation state (#1593)

Chip Input carried its chips in an <input type="hidden">, which the browser
leaves out of validation, so it could not be required or block a submit. The
chips now travel in a hidden <textarea> laid over the frame, with the same
comma-separated value and the id and name options on it. Like any disabled
field, a disabled chip input is no longer submitted.

- required makes an empty chip input block the submit; the browser's message
  shows over the field and the focus it gives the field goes to the text input.
- validationState (with the deprecated invalid and valid aliases), or an
  .is-invalid/.is-valid class in the markup, gives it a state, shown on the
  frame and as aria-invalid with the linked message on the text input;
  'invalid' blocks the submit. A user change of the chips drops a given state,
  a change from code keeps it, and setConfig({ validationState }) sets it again
  without rebuilding.
- What a validation reports shows the same way, a message can be named in
  data-coreui-invalid-feedback on the chip input, and a native form reset puts
  back the chips the field started with, the same elements, writes them into
  the field and fires change.coreui.chip-input when they changed.
- ChipSet sends its change event through _triggerChange(), and the form
  validation util gains createValueField, configureValueField, writeValueField
  and dispatchValueChange for the components that carry their value in a
  hidden field. Its feedback lookup treats a .chip-input as the element the
  layout places the messages around, and a frame that is a .form-field child
  as reaching that field.

Raises the bundlewatch ceilings of the six JS bundles. Measured with gzip -9
on both builds, the change adds 2.57 kB to coreui.bundle.js, 2.56 kB to
coreui.esm.js and 2.58 kB to coreui.js, and 1.04 to 1.06 kB to their minified
builds.

7550 of 8130 branches covered (92.87%)

Branch coverage included in aggregate %.

163 of 164 new or added lines in 3 files covered. (99.39%)

13070 of 13366 relevant lines covered (97.79%)

1629.12 hits per line

Uncovered Changes

Lines Coverage ∆ File
1
95.56
1.77% js/src/chip-input.ts
Jobs
ID Job ID Ran Files Coverage
1 37842834951.1 08 Oct 2026 08:55PM UTC 82
95.92
GitHub Action Run
Source Files on build 37842834951
  • Tree
  • List 82
  • Changed 3
  • Source Changed 3
  • Coverage Changed 3
Coverage ∆ File Lines Relevant Covered Missed Hits/Line Branch Hits Branch Misses
  • Back to Repo
  • Github Actions Build #37842834951
  • 4f188309 on github
  • Prev Build on v6-dev (#37833068463)
  • Next Build on v6-dev (#37853764964)
  • Delete
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE TRIAL · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc