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

coreui / coreui-pro / 42619296562
97%
main: 94%

Build:
Build:
LAST BUILD BRANCH: fix/avatar-link-underline-v6
DEFAULT BRANCH: main
Ran 09 Nov 2026 12:45PM UTC
Jobs 1
Files 92
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

09 Nov 2026 12:42PM UTC coverage: 96.659% (+0.006%) from 96.653%
42619296562

push

github

web-flow
feat(Calendar, DateRangePicker, DateInput): close the date family for v6 (#1813)

* fix(DateInput): read a pasted ISO date in ISO order

getSectionsFromString handed digit groups to the sections in order, so
0026-06-15 in dd.MM.yyyy put 0026 into the day and gave 26.06.0015. Only a
year section now takes a group longer than two digits, so that text goes to
getLocalDateFromString, which reads the ISO order. In a locale whose date has
an extra part, such as bg-BG, the fallback counted the parts and ignored any
ISO date; an ISO date now skips that count.

* refactor(Calendar): take the selected tab stop from the selection, not from a class

setRovingTabIndex read the selected target back from the selected class the
calendar had just drawn. isTargetSelected now answers from the start and end
with the rule that draws the state, and the DOM only maps data-coreui-date to
the element.

* refactor(DateInput): build the value field with createValueField

The field was built by hand, with its own focusin listener and its own copy of
the attributes and form options. createValueField and configureValueField give
it the same attributes and the same forwarding to the first empty section.

* refactor(forms): share the overlay of a value field in one mixin

ChipInput, DateInput, OtpInput and MultiSelect each carried the same block. The
compiled CSS differs only in where resize: none sits in two rules. Combobox
keeps its own block because its field is one pixel wide.

* feat(Calendar, DateRangePicker): add allowDisabledDatesInRange

A range that crossed a disabled date was always cleared, which suits a hotel but
not a flight, where only the two travel days have to be free. The new option,
off by default, skips that check, also for wholly disabled periods. A disabled
date still cannot be picked as an end, the disabled dates in between stay
disabled, and the value holds only the two ends.

8369 of 8878 branches covered (94.27%)

Branch coverage included in aggregate %.

24 of 24 new or added lines in 4 files covered. (100.0%)

14023 of 14288 relevant lines covered (98.15%)

2231.53 hits per line

Jobs
ID Job ID Ran Files Coverage
1 42619296562.1 09 Nov 2026 12:45PM UTC 92
96.66
GitHub Action Run
Source Files on build 42619296562
  • Tree
  • List 92
  • Changed 4
  • Source Changed 4
  • Coverage Changed 4
Coverage ∆ File Lines Relevant Covered Missed Hits/Line Branch Hits Branch Misses
  • Back to Repo
  • Github Actions Build #42619296562
  • 71367e22 on github
  • Prev Build on v6-dev (#42597445739)
  • Next Build on v6-dev (#42649210262)
  • 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