coreui / coreui-pro / 36843232483

96%

main: 94%

push

github

refactor(Range): move the range math to util/range (#1503)

* refactor(Range): move the range math to util/range

The order and distance of the thumbs, the nearest thumb to a press, the
pressed ratio, the thumb width, the stacking of the thumbs and the tick
positions move from range.ts to js/src/util/range.ts, exported as
@coreui/coreui-pro/utils/range, so the React and Vue editions import them
instead of keeping copies. The module also carries sanitizeValue, the
browser's sanitization of a range value, which the framework editions need
to render a value before the input holds it.

Range keeps its behaviour; a tick whose value is not a finite number is now
left out instead of breaking the tick grid.

* build: raise the unminified JS budgets for util/range

Measured with gzip -9 against v6-dev at 9a0cae504: coreui.bundle.js
+1751 B, coreui.esm.js +1695 B, coreui.js +1760 B, almost all of it the
JSDoc of the new util module, which the unminified bundles keep. The
minified bundles grow by 165-176 B and stay under their budgets.

* fix(Range): match the browser in util/range and name the util UMD globals

getTickPositions reads an object's value as a number again, so a tick
from a JSON data attribute ({"value": "50"}) sits at 50 as it did before
the move; only a value that is not a number is left out. sanitizeValue
counts the steps in decimals, as the browser does, so 0.15 with a 0.1 step
is 0.2 rather than 0.1, and it treats a max below min and a value that is
not finite the way the input does.

The per-file UMD builds named a util after its file, so util/range.js and
util/calendar.js took the Range and Calendar globals of the components and
the component read its helpers from itself. A util named like a component
now registers as RangeUtil or CalendarUtil.

The minified JS budgets go up by 0.25 KB: after this PR coreui.min.js had
24 B left by bundlewatch's own measure (+154 B for the move, gzip-size).

* fix(Range): drop ticks that are not finite and ta... (continued)

6555 of 7105 branches covered (92.26%)

Branch coverage included in aggregate %.

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

11692 of 11985 relevant lines covered (97.56%)

924.1 hits per line