KamoCRM

Strengthen hrOverview id-precision and attendance-state coverage

Testkamo-internal
Shipped
12 ஆகஸ்ட், 2026 அன்று 4:53 PM UTC
Author
kamo
Commit
e941fb5

The precision test used a 15-digit memberId, which round-trips through Number() losslessly and never proved the join key stays a string. Switch to an id past Number.MAX_SAFE_INTEGER and add a case with two distinct ids that collapse to the same double under Number() coercion, so a numeric join key now fails the test by merging two members instead of just printing a rounded id. Also cover attendanceState's untested branches (SUBMITTED -> 'open', default -> 'clear') and formatBytes's MB/GB boundary and non-finite guard.

All changes

Like what you see shipping?

All of it arrives in your workspace on its own. Start on the free plan and read this page again in a month.

Start Free ForeverView Pricing