Skip to main content

ripplearc_coreui 0.42.0 copy "ripplearc_coreui: ^0.42.0" to clipboard
ripplearc_coreui: ^0.42.0 copied to clipboard

A Flutter design system package with design tokens and basic components.

Changelog #

0.42.0 CoreStatusBadge and its colour, radius and icon size tokens #

โœจ Features #

  • CoreStatusBadge: a small pill that tags a value with its status, in three looks Figma draws: the 24 dp orange warning pill (optional 14 dp info icon), the 20 dp compact warning badge, and the 22 dp grey neutral tag. variant (CoreStatusBadgeVariant.warning / neutral) and size (CoreStatusBadgeSize.regular / compact) select the look, and an assert refuses the pairings Figma does not draw. The heights are minimums, so a badge grows with the user's text size. The label is passed in by the app and is cut with an ellipsis when it does not fit. onInfoTap with infoSemanticLabel turns the info icon into a labelled button, as the storyboard has it open the explanation of the tag; without them the icon is decorative (CA-1159)
  • AppColorsExtension.textWarningStrong (light orange700 #B03C00, dark orange200 #F7B999): orange text that reaches 4.5:1 on the orange badge fills in both themes. The existing textWarning reached only 3.98:1 in the light theme and 4.24:1 in the dark one (the orange text token that CA-1159 added)
  • AppColorsExtension.lineOrange (light orange200, dark orange300): the orange outline of the warning badge
  • AppColorsExtension.textGrayMid (light gray500, dark gray300): the grey text of the neutral tag. The dark value is gray300 because gray400 reaches only 4.06:1 on the dark grey fill
  • CoreRadius (radius6, radius8): corner radius tokens, exported from the package
  • CoreIconSize.size14: the 14 dp info icon size
  • Showcase: a Status Badge screen in the example app and a component doc

๐Ÿ“ Design notes #

The 10 and 11 dp side padding and the 22 dp neutral height wait on CA-1238. The ticket text lists a "โœ“ Your rate" variant. The storyboard has a cost saved as your default carry no badge, so it is not built. Figma also draws "Estimated" and "Your rate", but no screen uses them, so neither is built.

๐Ÿงช Tests #

  • Badge, regular warning pill: label, height, width, padding, icon on and off, icon size and gap, fill, outline, radius, text style, light and dark colours, growth at a large text size, no overflow when squeezed, and the info tap (hit area, a tap in the right padding, labelled button, same size as the decorative icon). Compact and neutral looks: height, padding, fill, outline, radius and label colour. The asserts. A11y: one announced label, no actions on a decorative icon, a labelled button on a tappable one, the text contrast guideline, 3:1 icon contrast on the regular warning pill (the only look with an icon), and 4.5:1 label contrast for every variant and size in both themes. Goldens: light and dark with all four states
  • Tokens: all three new colours in both themes, through copyWith and lerp; 4.5:1 contrast of textWarningStrong on both orange fills and of textGrayMid on the grey fill, in each theme; CoreRadius and CoreIconSize.size14 values. The colour and icon size swatch goldens gain the new tokens

0.41.0 CoreUnderlineTextField #

โœจ Features #

  • CoreUnderlineTextField: a text field drawn as a label over a value with a single rule beneath it and no border, for the dense stacked forms of the "New material, labor or equipment cost" screens (CA-1158). A sibling of CoreTextField, not a replacement. The underline is lineDarkOutline at rest and outlineHover on focus, 1px, and statusError for an error. It takes a placeholder (hintText), a controller or initialValue, a focusNode, keyboardType, textInputAction, inputFormatters, maxLength (no counter), autofocus, onChanged, onSubmitted and onTap, and owns no user-facing string
  • CoreUnderlineTextFieldSize: regular (12/16 label over a 16/24 value, 1px underline, 54px tall), compact (the same with the underline 2px closer to the value, 52px tall, for the fields of an open editor panel such as waste, burden, delivery and note) and large (14/20 label over a 24/32 semibold value, 2px lineMid underline, 66px tall) for a form that asks a single question
  • Prefix, suffix and unit: prefixText ($), suffixText (%) and unitText (days, /gal) are drawn by the field around the typed text, so an empty field still reads $ with a caret, backspace can never delete it, and the controller holds only what the user typed. The value hugs its text when something follows it, and the prefix, value, suffix and unit share one text baseline as the design draws them
  • Slots: labelTrailing (a badge beside the label, which keeps the field's height), inlineAccessory (a unit chip 12px after the value) and trailing (a lookup button at the far end of the row). The row grows to fit a taller widget and centers the value against it
  • Helper and error lines: helperText draws an info icon and a 12/16 line 8px under the underline, which adds 24px to the field. errorText (null or empty means no error) replaces it, turns the label, underline, icon and line to the error colors, keeps the underline red on focus, and is announced as a live region. The caller decides when to show it
  • States: enabled: false dims the field and stops focus and taps; readOnly keeps the normal look and refuses edits; selectAllOnFocus selects the value so the first digit typed replaces it; showCursor turns the caret off for a value on an own number pad. The caret takes 2px of room only while it shows
  • Text size: the label row and the value row are minimum heights, so they grow with the user's text size and the label is never cut or drawn over the value
  • Underline text field showcase screen in the example app and a component doc

๐Ÿ“ Design notes #

The focus underline is outlineHover (#003A54 in light mode), which is the value the design draws; outlineFocus is the caret. The disabled colors follow the Figma Text Field Line Disable variant. The design draws the % of a waste field as part of the value; the storyboard calls it a soft fixed suffix with no cursor, so suffixText is soft and a waste field passes showCursor: false. The placeholder is textDisable as drawn, about 2.5:1 on a white page, below the 4.5:1 WCAG asks of text; it is the token CoreTextField already uses for its hint. The text field's accessibility node is 48px tall though the value row is drawn 24px or 32px tall, so the field meets the minimum tap target without changing the design's spacing.

๐Ÿงช Tests #

  • Content, sizes and offsets against the design's numbers, growth at a large text size, colors in both themes, underline rest and focus, tap-to-focus on the label and underline, a replaced focus node, prefix, suffix, unit, hugging, slots, helper and error lines, disabled and read-only, select-all on focus, onTap, and caret room
  • A11y: tap target, label and contrast in both themes for all three sizes, the announced label and value, error as a live region, disabled and read-only flags, and a 48px accessibility node
  • Goldens in light and dark: rest, focused (12 states), affixes and slots, compact, helper and error lines, and disabled and read-only

0.40.0 CoreNumberKeypad #

โœจ Features #

  • CoreNumberKeypad: the app's own number pad for a plain number field. Four rows of pill keys (7 8 9, 4 5 6, 1 2 3, . 0 โŒซ) and, under them, an outlined put-back button and a filled confirm button whose labels the caller sets (Clear or Back to 10%, and Add to estimate). Each key and button has its own callback (onDigitPressed with the digit, onDecimalPressed, onBackspacePressed, onClearPressed, onConfirmPressed), so the keypad knows nothing about the field. isConfirmEnabled greys out the confirm button. CoreNumberKeypad.height (368 dp) is there for a sheet that reserves room for the keypad (CA-1253)
  • CoreDigitInput.textStyle replaces the label style, which by default is titleLargeRegular scaled to the key's height. The colour stays textHeadline
  • CoreControlButton.isNeutral draws the key on the digits' grey with a dark grey face, so it does not compete with a filled button beside it
  • Number keypad showcase: a value typed with the keypad, cleared and added

๐Ÿ“ Design notes #

Built from the storyboard's number pad (CUJ 4 "Keys up", cuj456_screen.css .kbd), which is newer than Figma and has no Figma variant yet. Keys are 68 dp tall with 4 dp gaps and a 16 dp side inset, and the buttons sit 16 dp below the keys. The backspace key is grey like the digits, not the calculator's dark blue, so the confirm button is the only filled key (storyboard, approved by the owner 2026-10-03). The ticket and Figma show it dark blue. The digits use titleLargeMedium (20 dp), not the calculator's height-scaled 23.8 dp. The keys reuse the calculator's CoreDigitInput and CoreControlButton, so they press and give haptic feedback the same way.

๐Ÿงช Tests #

  • Keypad: each digit, the decimal point, backspace, both buttons, a disabled confirm button that ignores taps and reads disabled while the other keys still work, the key order, 124 x 68 keys and 188 x 68 buttons on a 412 dp phone, narrower keys on a 320 dp phone, and no overflow at 200 % text with a long put-back label. Keys: textStyle replaces the scaled style and keeps the colour, the default still scales, isNeutral colours in both themes, and delete stays dark blue without it. A11y: tap target, label and contrast guidelines in both themes, confirm enabled and disabled. Goldens: light and dark

0.39.0 CoreDetailsRow #

โœจ Features #

  • CoreDetailsRow: a rounded grey row that folds a detail of a form away โ€” a label, a bold value, an optional link-style action after a dot, and a chevron. A tap anywhere on the row but the action calls onToggle; while expanded, child shows under the row inside the same card. The caller owns expanded, so the action can open the row too. actionLabel and onAction come together (asserted). It replaces the Delivery row the app draws by hand in the equipment form (CA-1252)
  • Details row showcase: a Delivery row with an action and a Waste row without one

๐Ÿ“ Design notes #

Built from the storyboard's .mod / .modx (cuj456_screen.css) and the Figma "Details Row" set 65708:169539: a 48 dp row, 12 dp corners, a 1 dp lineLight edge on backgroundGrayLight. The label starts 16 dp in, as in Figma; the chevron's 48 dp square ends at the card's edge, which centres the icon 24 dp in, as in the storyboard. The dot sits in an 18 dp slot (Figma's 10 dp box with 4 dp each side). The whole row is the toggle's tap zone; the action's zone is at least 48 dp wide. The storyboard's Estimated tag on a folded row (round 18, Q33) is not part of this row yet.

๐Ÿงช Tests #

  • Row: label and value in one line, the action after a dot and no dot without one, a tap on the value, the chevron or the empty middle toggles, the dot's 18 dp slot, a tap on the action calls onAction and does not toggle, the panel hidden while folded and under the row while expanded, the chevron's turn, a 48 dp row with the chevron 24 dp in, a long value that ends in an ellipsis and keeps the action, the action assert, and the toggle and action semantics with the expanded state. A11y: tap target, label and contrast guidelines folded and expanded in both themes; each text colour holds 4.5:1 and the chevron 3:1 on the card. Goldens: light and dark

0.38.0 CoreOutlinedIconButton #

โœจ Features #

  • CoreOutlinedIconButton: a square icon button, a 36 dp box with a 1 dp lineMid edge, 8 dp corners and a 20 dp iconGrayMid icon, centred in a 48 dp square that takes the taps. It replaces the look-up button the app draws by hand beside the Rate and Amount fields of the equipment form. icon, onTap and semanticLabel are required: the button has no visible text, so the label is its only name (CA-1252)
  • Button showcase: the look-up button

๐Ÿ“ Design notes #

Built from the storyboard's .iconbtn (cuj456_screen.css): 36 dp, 8 dp corners (CoreSpacing.space2), a 1 dp --line-mid edge and a 20 dp magnifier. The box has no fill, so it takes the colour of the sheet under it. The button takes 48 ร— 48 dp of layout, so a row that holds it is at least 48 dp tall.

๐Ÿงช Tests #

  • Button: the icon's size and colour, the 36 dp box with its edge and corners, the 48 dp tap square, a tap on the box and a tap on the margin each call onTap once, and one button node named by the label. A11y: tap target, label and contrast guidelines in both themes; the icon holds 3:1 on the page in both themes. Goldens: light and dark

0.37.0 CoreListRow.action #

โœจ Features #

  • CoreListRow.action: a leading icon and a title, the icon in iconDark and the title in textLink at bodyLargeSemiBold (16 sp, as Figma's Action row), e.g. "+ New equipment cost" under a list of recent rates. The icon sits in the same 20 dp slot as .selectable's check, so its title lines up with every selectable row's (the plain row has no slot). Takes no subtitle or value, and onTap is required (CA-1204)
  • List row showcase: the action row under the plain list

๐Ÿงช Tests #

  • Action: the icon in iconDark, the title in the link colour at 16 sp, the title at the same x as a selectable row's, tap, and a screen reader hears a button with no selected state. A11y: tap target and label guidelines in both themes. Goldens: light and dark gain the action row

0.36.0 CoreListRow.selectable #

โœจ Features #

  • CoreListRow.selectable: a row in a pick-one list. It keeps a 20 dp check slot even when unselected, so rows don't shift when the pick moves. A selected row fills backgroundBlueLight, turns its title textLink, shows the check and reports its selected state to a screen reader (CA-1204)
  • List row showcase: a pick-one list from the Equipment "Look up a rate" screen

๐Ÿ“ Design notes #

Built from the storyboard's Equipment "Look up a rate" frame (cuj6-equip-4-lookup). It shares the plain row's geometry.

๐Ÿงช Tests #

  • Selectable: the empty check slot keeps its width so selected and unselected titles start at the same x, the selected fill, check and title colour, and the selected state, picked or not. A11y: a selected row meets the tap target and label guidelines in both themes, and every text colour holds 4.5:1 on the selected fill in both themes. Goldens: light and dark gain selected and unselected rows

0.35.0 CoreListRow #

โœจ Features #

  • CoreListRow: a tappable list row with a title, an optional subtitle under it, and an optional value at the end (value plus a smaller unit, e.g. $145.00 /day). The row pads its content by CoreSpacing.space2 and is at least 48 dp tall; the list around it supplies the page inset. The default screen-reader label is the visible texts in order, or semanticLabel. The value takes at most half the row and shrinks rather than overflow at large text sizes; the title wraps (CA-1204)
  • List row showcase: plain rows from the Equipment rate screens

๐Ÿ“ Design notes #

Built from the storyboard's Equipment "Your recents" frame (cuj6-equip-1-recents), which the app built as one-off rows in CA-1151. The 2 dp gap between title and subtitle is the storyboard's; CoreSpacing has no step that small.

๐Ÿงช Tests #

  • Row: texts, no leading slot and no fill on a plain row, a unit without a value is dropped from the row and its screen-reader label, an empty subtitle is left out of the label, tap, 48 dp minimum height, default and custom screen-reader labels with the tap action kept, and a wide value at 200 % text on a 320 dp row shrinks instead of overflowing. A11y: tap target and label guidelines in both themes, and every text colour at 4.5:1 on the page in both themes. Goldens: light and dark

0.34.0 The acknowledgement toast #

โœจ Features #

  • Toast.acknowledgement: the dark toast that reports a finished task โ€” "Added to Bedroom 2". A 24 dp statusSuccess circle with a 15.6 dp wide white tick (65 % of the circle) and one line of bodyMediumSemiBold text on backgroundDarkGray, with a 12 dp corner radius and the new CoreShadows.floating. It has no action and no close button, and it is a live region, so a screen reader reads it when it appears (Figma component 65687:157849, CA-1256)
  • CoreToast.showAcknowledgement: shows it in the overlay and removes it after duration, 4 s by default
  • CoreShadows.floating (0/8/24, CoreShadowColors.shadowGrey28): the shadow that lifts a dark surface off the page
  • Toast showcase: an acknowledgement preview and a button that shows a live one

๐Ÿ“ Design notes #

In the dark theme Figma's Background/Dark Grey and Text/Inverse both resolve to gray900, the dark page colour, so the toast would vanish. The dark theme draws it on backgroundGrayMid with textHeadline text, and the tick turns dark (textInverse): white on the dark theme's green400 is 2.3:1, under the 3:1 a graphic needs. The padding and gap use the nearest CoreSpacing steps (12/16, 12) instead of 13/15 and 11, and a 50 dp minimum height keeps the frame's 384ร—50.

๐Ÿงช Tests #

  • Widget: the acknowledgement shows its message with no close button and nothing to tap, announces the message once as a live region, stands off the page in both themes, and keeps its tick at 3:1 against the circle in both themes. A11y: it meets the guidelines in both themes. CoreToast: showAcknowledgement shows no close button and leaves after 4 s, or after the duration it is given. Golden: toast_component gains the acknowledgement

0.33.1 Light success green matches Figma #

๐Ÿ› Fixes #

  • CoreStatusColors.success and CoreIconColors.green (light theme) are green500 (#009E69), not green600. Figma draws State Color/Success and Icon Color/Green as Green/500, and the dark values already matched. These two tokens draw graphics only (a tick, a switch track, an icon), where green500 on white is 3.4:1 against the 3:1 a graphic needs (CA-1256). One use falls short: the light success toast draws its tick on alertGreen (green100), which is 2.75:1 (it was 4.06:1). The tokens still follow Figma
  • CoreFunctionKeyBottomSheet: the Imperial label is text, so it uses textSuccess (green600, 4.5:1 or better on white) instead of iconGreen, which would fail 4.5:1 now. Its colour does not change
  • CoreCheckRowItem docs and showcase: the avatar initials use textSuccess for the same reason
  • CoreAvatar centres its child. The fixed-size Container had no alignment, so it stretched a Text child to the full circle and drew the letter at the top left; every default CoreCheckRowItem avatar showed this. A child that centred itself, such as an icon, does not move

๐Ÿงช Tests #

  • Goldens regenerated where the light green shows: color tokens, avatar, check row item, function key sheet, preferences sheet, switch and toast
  • The check row golden draws the initials in textSuccess, as the docs say, and its light and dark goldens are regenerated for the centred letter

0.33.0 The empty estimate summary card, and long names #

โœจ Features #

  • CoreEstimateSummaryCard.empty (title, note): the card before the line can total. It has four parts instead of five: the caption, a dash in place of the amount (CoreEstimateSummaryCard.emptyAmount), the rule, and the note naming the missing field, e.g. "Needs a rate before it can total" (storyboard "Unpriced state", CA-1255). A screen reader skips the dash and reads the note
  • CoreEstimateSummaryCard fits long text. A long estimate name ellipsises first, so "total $2,993.62 โ†’" stays whole. The new total takes at most half the row, and the before text at most 70 % of what is left, and both shrink to fit instead of clipping. The line total shrinks to its 40 dp slot the same way
  • Estimate summary card showcase: the empty card

๐Ÿงช Tests #

  • Widget: the empty card shows the dash and the note and no totals, and is 117 dp tall (four parts). A long name ellipsises while the before text and the new total stay whole, with the new total against the right padding. On a 200 dp card the amounts shrink to one line inside the padding. A11y: every text on the empty card is at least 4.5:1 on the fill in both themes, and the empty card reads the note but not the dash. Goldens: core_estimate_summary_card gains a long name and the empty card

0.32.0 The estimate summary card #

โœจ Features #

  • CoreEstimateSummaryCard: the "Adds to this estimate" card above a cost form's Add button (Figma "Estimate Change" 66335:151611, used by the material, labor and equipment forms, CA-1255). It shows the caption, the line total in 32/40 semibold with -0.32 letter spacing, an optional extra charge, a rule, then the estimate's name and its total before the change on the left and the new total on the right. Every string arrives formatted and localised. The card is 125 dp tall without an extra charge, as in the frame: radius 14, padding 13/15/12/15 and a 1 dp gap between rows, on backgroundBlueLight. It is one live region, so a screen reader reads the new totals as the user types
  • CoreEstimateSummaryCharge (label, amount): the "incl. delivery +$85.00" row, a 24 dp row under the amount
  • lineBlue (CoreBorderColors, CoreDarkBorderColors, AppColorsExtension): the rule on a backgroundBlueLight panel. Light is Figma's Boarder Color/Line Blue #C7ECFA, which sits between blue50 and blue100 and has no palette step. Dark is blue800, one step lighter than the dark panel's blue900. The storyboard asks for the rule to be coloured from the panel, not from the grey used on white
  • Estimate summary card showcase: the card with and without an extra charge

๐Ÿ“ Design notes #

Figma draws the "Bedroom 2 total $2,993.62 โ†’" text in textDisable, which is 2.4:1 on the blue fill in light and 2.6:1 in dark, under WCAG's 4.5:1. The card uses textBody (7.2:1 and 8.9:1) instead. The padding, radius and gaps are Figma's own numbers, because none of them is a CoreSpacing step.

๐Ÿงช Tests #

  • Widget: the card shows every string, is 125 dp tall without a charge and 150 with one, puts the charge under the amount and the new total against the right padding, and draws the amount at 32 with -0.32 spacing. In both themes it uses the blue fill, radius 14, a lineBlue rule and textBody for the before text. A11y: every text on the card is at least 4.5:1 on the fill in both themes, checked one text at a time because the merged node lets Flutter's contrast guideline pass any grey; the card is one live region that reads the caption, the amount, the charge and the new total. Theme: lineBlue in light and dark. Goldens: core_estimate_summary_card light and dark, and the colour token sheets gain lineBlue

0.30.0 CoreCalculatorChip inert state and the stale answer #

โœจ Features #

  • CoreCalculatorChip.inert (default false): dims the chip to CoreCalculatorChipTheme.inertOpacity, makes it ignore onTap and onLongPress and reports it disabled to a screen reader, while keeping the look of its type โ€” a ร—5 keeps its operator and an answer keeps its label. The chips before an open bracket, and the chips after a reopened one, wait like this until the bracket closes (UX design doc term 2.22, Section 7 "Editing a bracket", walkthrough 12.8). Unlike disabled it is a state over any type, not a look of its own (CA-1189)
  • CoreCalculatorChipType.stale: an answer that is out of date because a chip before it is being edited. The result fill under a dashed lineDarkOutline edge (prototype .t-stale), showing CoreCalculatorChip.stalePlaceholder (โ€”) in place of a number so no out-of-date figure can be read; the label stays, so it reads Calc โ€”. Takes no value (asserted) and stays interactive unless inert. The dash marks a chip that is unfinished (prototype decision Q3), and dashes grey rather than teal because nothing is being typed into it. The placeholder is punctuation a screen reader skips, which would leave "Calc" and no sign that the answer is pending, so a stale chip requires semanticsLabel ("Calc, pending"; asserted)
  • CoreCalculatorChipTheme.factorColor takes inert (default false): an inert chip draws its factor in the colour of its text, so the operator before a waiting ร—5 stays as readable as the number
  • CoreCalculatorChip.effectiveOpacity exposes the opacity the chip is drawn at, for tests
  • Calculator chip showcase: the bracket section becomes the three tapes of walkthroughs 12.6 and 12.8 โ€” an open bracket with the 2 waiting, the closed bracket with its Calc 70, and the reopened bracket with ร—5 waiting and Calc โ€”

๐Ÿ“ Design notes #

The prototype dims a waiting chip to 55 % (.t-frozen), which drops the typed teal to 2.7:1 against the page. inertOpacity is 70 %, which keeps every variant's text and factor at or above the 3:1 floor WCAG 1.4.11 sets for user-interface components in both themes โ€” a test composites all nine variants' value, label and factor over their fills at that opacity and asserts the ratio; WCAG 1.4.3 exempts an inactive control from the 4.5:1 text floor, and an inert chip reports itself disabled so the automated contrast guideline treats it as one. The factor holds the floor because an inert chip draws it in the text colour: the light theme's iconOrient and iconRed sit between 3.5:1 and 4:1 on their fills and would fall to 2.4โ€“2.8:1 at 70 %. The teal edge of the typed variants holds 3:1 against the page and the fill as well; the grey and red hairlines of the filled variants are outside the floor, at 1.2โ€“2.3:1 on their fills before any dim. The 70 % against the prototype's 55 % is open with design, recorded on CA-1189.

๐Ÿงช Tests #

  • Chip: an inert chip keeps its text and factor, ignores tap and long-press, and is drawn at inertOpacity while a live chip is not; inert over a result keeps its label. The Opacity the chip builds carries effectiveOpacity, inert and live, and an inert chip's factor takes the text colour. A stale answer reads its label and the placeholder and never a number, announces the caller's semanticsLabel, refuses a value, refuses to be left without a semanticsLabel, and stays interactive unless inert. Theme: the stale tokens in light and dark; the dashed outline resolves for dashed, bracketOpen and stale only. A11y: stale meets text contrast in both themes; an inert chip reports isEnabled false with no tap or long-press action; an inert tape passes the guidelines in both themes; and for all nine types in both themes the dimmed value, label and factor composited over the dimmed fill keep at least 3:1, as does the teal edge of the four typed variants against the page and the fill. Goldens: light and dark gain Stale, Inert and Stale + inert cells

0.29.0 CoreCalculatorChip bracket looks #

โœจ Features #

  • CoreCalculatorChip: two bracket variants for the one chip that holds a whole bracket (UX design doc term 2.22, Section 7, walkthroughs 12.6 and 12.8). CoreCalculatorChipType.bracketOpen is the bracket still being typed into: the active green under a dashed teal edge, drawn without its closing bracket. CoreCalculatorChipType.bracketClosed is the same chip once closed: solid teal on backgroundBlueMid, with its closing bracket, and a tap on it is how the bracket reopens. The chip draws the brackets itself โ€” value is the text inside them, so 3ร—4 reads (3ร—4 while open and (3ร—4) once closed and the missing bracket can never disagree with the type; displayedValue exposes the drawn text. The operator before the bracket is the factor, as on every other chip. A closed bracket requires a value (asserted): the calculator removes an empty bracket rather than draw one (CA-1189)
  • CoreCalculatorChip.semanticsLabel replaces the screen-reader label built from label and the drawn value, and tapSemanticLabel is the tap hint ("double tap to โ€ฆ"), which requires onTap as longPressSemanticLabel requires onLongPress. A bracket's state is punctuation a screen reader skips, so the app says it in words โ€” "open bracket, 3 times 4", and "reopen the bracket" on the closed chip. Both are localised by the caller
  • CoreCalculatorChipTheme.isDashed and edgeColor: one place decides which variants dash and what colour their edge is; borderColor (transparent when dashed) and dashedOutline both read them, so a variant can no longer be solid and dashed at once, or neither
  • Calculator chip showcase: a Bracket section with the open and the closed chip

๐Ÿ› Fixes #

  • CoreCalculatorChip: a chip with a value but no factor and no label drew the space1 gap meant to separate the value from what precedes it, so its value sat 4 dp off-centre โ€” visible on the Dimension error cell and on a bracket that starts a chain. The gap is drawn only when a factor or a label precedes the value; the two error cells in the chip goldens shift by 4 dp

๐Ÿ“ Design notes #

The bracket chips follow the prototype (.t-group / .t-group-open); there is no Figma variant. The open fill is the prototype's #cffce4 exactly (backgroundGreenMid); the closed fill is the nearest token to its #d6eeff (backgroundBlueMid, #dcf5ff). Both sit flat like the other filled chips โ€” the prototype draws no shadows โ€” and keep the 1 px edge every variant shares against the prototype's 1.5 px.

๐Ÿงช Tests #

  • Chip: an open bracket draws (3ร—4 and nothing ending in ), a closed one (3ร—4), a bracket just opened reads (; the semantics label reads the bracketed text; a tap on a closed bracket reaches onTap; long-press fires on both. Theme: both variants' tokens in light and dark; the dashed outline resolves for dashed and bracketOpen only. A11y: both variants meet text contrast in both themes. Goldens: light and dark gain the two bracket cells

0.28.0 CoreKeyboard bracket key #

โœจ Features #

  • CoreKeyboard: the bottom-left key is the ( ) bracket key, ControlAction.paren, in the place the โ‹ฎ control held. It reaches the consumer through onControlAction like the other controls and carries the stable test key calc_key_paren. The key is a toggle the tape reads, not the key: its face never changes, the first press opens a bracket and the next press closes it (UX design doc 1.3 and key card 3.6). parenEnabled (default true) dims the key, drops its tap action and reports it disabled to a screen reader, so the value editor can keep a bracket out of a single number โ€” CoreValueEditorSheet passes false (CA-1189)
  • CoreControlButton: enabled (default true) is the same switch on a control built on its own; a disabled control announces no hint, and disabling it while a finger is down releases the press without firing. ControlActionX.label is the text face of a control (( ) for the bracket key, null for the icon controls) and ControlActionX.icon returns null for the bracket key
  • CoreKeyboard.parenSemanticLabel and parenSemanticHint replace the bracket key's English screen-reader label and hint with the app's localised strings. CoreControlButton.semanticLabel and semanticHint do the same for a control built on its own, and CoreValueEditorSheet.parenSemanticLabel (also on show and showSingleValue) names the key the editor keeps disabled. All are optional: left out, the key announces the English Bracket button the way the other keys announce theirs
  • Keyboard showcase: a switch above the keyboard disables the bracket key the way the value editor does, and the bracket key takes its screen-reader label and hint from the showcase

โš ๏ธ Breaking change #

  • ControlAction gains paren, so an exhaustive switch over it no longer compiles until it handles the new case โ€” the calculator bloc's moreOptions arm did nothing, and the bracket handler is its replacement. CoreKeyboard no longer renders the โ‹ฎ control and never sends ControlAction.moreOptions; the value stays, deprecated, so an existing moreOptions arm keeps compiling, and its removal is tracked by CA-1197

๐Ÿงช Tests #

  • Keyboard: the bracket key sits left of the zero key, sends paren on every press and keeps its face; parenEnabled: false silences the bracket key and no other; the moreOptions key is gone. Control button: the ( ) face, the semantics label and hint, a disabled control ignores taps and carries no tap action. Value editor: the bracket key is disabled. A caller's semanticLabel and semanticHint replace the English defaults on a control, the keyboard and both value editors, and the hint stays withheld while disabled. A11y: the bracket key meets the tap-target and label guidelines in both themes, enabled, disabled and labelled by the caller. Goldens: the keyboard and value-editor goldens change at the bottom-left key only; the buttons grid adds an enabled and a disabled bracket key

0.27.0 Receipt toast and display-area session restore #

โœจ Features #

  • Toast.receipt: the self-dismissing confirmation the calculator shows when a session is banked โ€” "Saved to history ยท Calc 60ftยฒ" with Undo. One line of text rather than a stacked title and description, an outlined backgroundBlueLight surface with a space3 radius and no shadow, and an action instead of a close button. description is the lead and highlight the tail after a middot; onAction fires at most once and cancels the auto-dismiss; onClose is required, because it is the only way a receipt leaves the screen. duration defaults to 5 s and null holds the toast until something else removes it (CA-1042)
    • The action is a 48 dp CoreButtonSize.large pill rather than the ~29 dp the design draws, because a tap target under 48 dp is an accessibility defect; the frame is open with design
    • The receipt announces itself as a live region, and it does not start its timer while MediaQuery.accessibleNavigationOf is true โ€” it carries no close button, so a timed window a screen-reader user cannot reach in time is worse than no window
    • A long translated action label ellipsises itself instead of squeezing the message: the action may take 60% of the width it shares with the message, which leaves the message the other 40%
  • Toast.receipt: secondaryLabel / onSecondary add the quieter second action (View) beside Undo. The two travel together โ€” asserted in the factory and checked again at build, because an assert is gone in release and a control a screen reader cannot announce is worse than none. Either action answers the toast: whichever is tapped first reports, cancels the auto-dismiss and dismisses, and the other is locked out. View is an InkWell with its ink turned off, so the whole 48 dp box answers a tap and keyboard, D-pad and switch users can reach it; it renders in bodyLargeSemiBold at 85 % of textLink (CA-1042)
  • CoreDisplayArea: onPreviousSessionTapped(String id) reports a tap on a previous-session card so the consumer can restore that tape, with restoreSemanticsLabel naming the control for a screen reader โ€” asserted non-null whenever the callback is given. CoreHistorySessionData.id is the new optional identifier; a session without one, or with an empty one, stays the plain card older callers already pass. Ids must be unique across previousSessions. The card is an InkWell with its ink suppressed but its focus highlight kept, so keyboard, D-pad and switch users can reach it, and its contents sit under an IgnorePointer, an ExcludeFocus and a MergeSemantics, so a chip in a past session is inert to touch, to the keyboard and to a screen reader alike โ€” it can neither win the gesture arena, nor stay a tab stop, nor sit in the tree as an enabled button that answers nothing (CA-1042)
  • CoreToast.showReceipt: puts a receipt in the overlay and wires its dismissal to that entry. The widget owns the timer and CoreToast starts none of its own, so the 5 s window is never cut short by the 3 s default the other toasts use; disableTimers() and cleanup() behave as they do for every other toast. showError, showSuccess and showWarning keep their 3 s CoreToast timer (CA-1042)
    • CoreToast.showCustomToast takes a nullable duration: a null leaves the entry up until something else removes it, for a toast that owns its own dismissal. The 3 s default is unchanged, so every existing call behaves as before
  • Showcases: the display-area demo answers a restore tap with CoreToast.showReceipt naming the session that came back, so the tappable card and the receipt โ€” the two halves of CA-1042 โ€” demo together instead of echoing through a Material SnackBar (CA-1042)

โš ๏ธ Behaviour change #

  • Toast: an untitled toast is announced once instead of twice. Its semantics label is the title alone, and the description reaches the screen reader through the text it labels; before, an untitled toast used its description as the node label as well, so the description was read out and then read again (CA-1042)
  • Toast.receipt: the second action renders at 85 % of textLink rather than the design's 75 %. At 75 % it composites to #3C839D on the receipt surface โ€” 4.02:1, under the 4.5:1 WCAG AA floor โ€” and the component's own contrast guideline fails on it. Open with design
  • CoreToast: every overlay removal now goes through one idempotent path, and each onClose and timer carries the entry it was built with rather than reading whichever entry is current. Two defects go with it. Two toasts shown in the same frame left the first orphaned in the overlay, because an entry inserted in that same frame has not mounted yet and the old mounted check skipped it. And cleanup() followed by a new toast threw "An OverlayEntry should be removed only once" in debug builds, because cleanup() removed the entry but left it in _entry for the next call to remove again. A close tapped on a toast that has already been replaced is now ignored instead of taking the replacement off the screen (CA-1042)

0.26.0 CorePreferencesSheet and CorePreferenceOptionSheet #

โœจ Features #

  • CorePreferencesSheet: a bottom sheet body listing settings grouped into CorePreferenceSections, each row showing its label and current value and opening a single-choice sub-sheet (CA-1041). The sheet holds no persistent state โ€” it reports through onChanged(key, optionId) and the caller re-supplies sections, so the stored preference stays the single source of truth
    • CorePreferenceValue is sealed with two variants, because the rows do not all read the same way: CorePreferenceTextValue(label, isMuted:) renders textLink text (or textDisable when the preference is still a stub) and CorePreferencePillValue(label, isOn:) renders an outlined pill with a green or grey state dot, as System of units and Thousands separator do
    • initialKey deep-links to one row: it is scrolled into view before the first frame the user sees and marked for CorePreferencesSheet.emphasisDuration, the path a tapped fraction in a result takes to Fractional resolution. An unknown key opens the list at the top
    • A row with fewer than two options is inert โ€” it renders its value and opens nothing
  • CorePreferenceOptionSheet: the single-choice sub-sheet. Selection is local until the user taps Update, at which point onUpdate receives the chosen id and the sheet pops itself, so backing out of a setting leaves it unchanged. Update stays disabled until the pick matches one of options, so a selectedOptionId left over after the option set changed shows no ticked row and cannot be committed
    • CorePreferenceInfo { title, description, semanticsLabel, closeLabel } on a row adds an info button to the sub-sheet's header; opening it replaces the Update button with a Toast.info. The footer holds the taller of the two states, so the explanation does not grow the sheet under the thumb that opened it โ€” a row carrying an explanation reserves that height from the start, a row without one stays as tight as the button (Figma 62481:80137 and 62481:80158 are the same 354px container). The four fields travel as one object rather than loose optional parameters, so the button cannot be configured without its labels โ€” an interactive control with no semantics label is invisible to a screen reader (RULE 14)
  • CorePreferencesSheet forwards optionKeyOf and optionUpdateButtonKey to the sub-sheet, so a consumer can drive open-row โ†’ pick โ†’ commit entirely by key rather than by matching option labels as text (RULE 8)
  • The five preference model types (CorePreferenceRow, CorePreferenceSection, CorePreferenceOption, CorePreferenceInfo and both CorePreferenceValue variants) compare by value, so two equal-by-value instances are equal and hash alike. Lists compare element-wise, so a row is judged by the options it holds rather than by which list instance holds them
  • Showcase: the calculator's display preferences (UX design doc, Appendix C) with deep-link buttons to Fractional resolution and to the last row

๐Ÿ“ Design notes #

Built to Figma 62481:79132 ("Settings page"), which differs from the ticket's description: rows carry no chevron, the option sheet marks its choice with a check rather than a radio, and a choice is committed with a sticky Update button. The deep-link mark has no design of its own. The option sheet's back button uses CoreIcons.arrowLeft, as the design system has no chevron icon.

๐Ÿงช Tests #

  • Widget: an option reports nothing until Update commits it; a selectedOptionId matching no option cannot be committed; a pick the user made survives the same preference changing elsewhere, including when they land back on the value the sheet opened with; back leaves the preference untouched; the info button swaps Update for the explanation without changing the sheet's height, and needs both a title and a description; Update is disabled with nothing selected, commits the pick and dismisses the sheet, and stays disabled for a sheet opened on an id matching no option; initialKey lands on a row the fixture proves starts off-screen; an unknown key opens the list; the sheet does not update its own rows; a single-option row opens nothing
  • A11y: rows, the back button, the info button, option rows and Update all meet tap target, label and contrast guidelines in light and dark; an option row is announced as a button and as selected, and the decorative tick is excluded from semantics so it is not announced twice
  • Goldens: core_preferences_sheet_{light,dark}.png and core_preference_option_sheet_{,info_}{light,dark}.png

0.25.0 CoreValueEditorSheet gains a single-value mode #

โœจ New #

  • CoreValueEditorSheet: CoreValueEditorSheet.singleValue / showSingleValue edit one labelled value with an optional unit โ€” the sheet the calculator opens behind a dependent-key pill (sheet size, rate, waste, density) โ€” committing a CoreValueEditorResult and reporting through onSaved(String value, String? unit) (CA-1040).
    • Both modes share one widget and one keyboard wiring: internally the sheet is a list of fields, and single-value is a one-element list.
    • New unit seeds the unit a commit reports when the user never taps the unit row. Single-value only โ€” a debug assert rejects it on the multi-column constructor, where nothing would read it.
    • A unit key differs by mode: single-value records the selection and reports it separately, while multi-column keeps spelling it into the value the way 47.24in does, since SizeEntryResult carries no unit. This covers the keyboard's own unit column (Yards/Feet/Inch) as well as the unitOptions row โ€” it cannot be hidden, so it follows the same rule. Its / key, which exists to compose compound units inside the text, is ignored in single-value mode. The two controls report different vocabularies: the row gives back one of your unitOptions, the column its own label.

0.24.0 CoreValueEditorSheet: the size entry sheet becomes public #

โš ๏ธ Breaking changes #

  • CoreGeometryArea: CoreSizesTableData gains required-with-onSaved addResultLabel and editResultLabel, which name the entry sheet's commit key (CA-1040). They are separate from addLabel / editLabel, which title the sheet: the design's sheet reads "Edit size" while its key reads "Update".
    • Migration: add both to every CoreSizesTableData that sets onSaved. A debug assert names the omission.
  • CoreValueEditorSheet: resultLabel is required, replacing the widget's hard-coded 'Add' / 'Update'. Reachable through the deprecated SizeEntryBottomSheet typedef, so existing callers must supply it. unitGroupLabel is likewise required whenever unitOptions is set โ€” this package ships no user-facing English.
  • CoreGeometryArea: CoreSizesTableData.unitOptions and unitGroupLabel replace the entry sheet's hard-coded m / cm / mm row. They are user-facing strings, so the package no longer ships a default: a table that does not supply unitOptions renders no unit row.
    • Migration: pass unitOptions and a localized unitGroupLabel on any table whose entry sheet should keep its unit row; a debug assert names the omission.
  • CoreKeyboard / CoreResultButton: customLabel was declared and documented but never read, so customResultLabel had no effect and the result key always rendered its resultType โ€” the commit key showed "=" where the design asks for "Update". It is now honoured and rendered verbatim, preserving sentence case ("Update", not "UPDATE"). This changes what every existing customResultLabel caller displays, with no code change on their side, so audit those call sites on upgrade. An empty customLabel still falls back to resultType. Its screen-reader hint no longer claims the key calculates a result when the caller named it something else.

โœจ New #

  • CoreValueEditorSheet: SizeEntryBottomSheet is promoted out of CoreGeometryArea's private parts and exported from the barrel (CA-1040). SizeEntryBottomSheet remains as a deprecated typedef for one release.
    • New validator rejects a value, showing the message beneath the offending field and keeping the sheet open; editing that field clears it.
    • The sheet now survives being rebuilt with a different number of titles, which it could not do while it was private and only ever opened as a modal.

0.23.0 CoreGeometryArea renders several independently-configured tables #

โš ๏ธ Breaking changes #

  • CoreGeometryArea: the single-table parameters are replaced by tables: List<CoreSizesTableData>, so the calculator's detail panel can render the sizes, rates-and-waste and density tables together, each with its own callbacks (CA-1039)
    • Removed: sizesTableTitles, sizesTableData, sizesTitleLabel, addSizeLabel, editSizeLabel, dragHandleLabel, onSizesReordered, onSizeDeleted, onSizeSaved, and the defaultSizesTitleLabel / defaultAddSizeLabel / defaultEditSizeLabel / defaultDragHandleLabel constants
    • Migration: wrap the former arguments in a single CoreSizesTableData. Column titles become CoreSizesColumns, sizesTableData becomes rows, and the onSize* callbacks lose their prefix โ€” onSaved, onDeleted, onReordered. Also supply the new required id: unlike the rest it has no predecessor to map from, so it cannot be inferred from the old call โ€” see โœจ New below
    • CoreSizesTableData.title is required and has no English default. Titles interpolate the result they describe ('Sheet quantities for 180ftยฒ'), so they cannot be a package-level constant. This continues the 0.15.0 move of localization ownership to the consuming app
  • Affordances are now driven by their callbacks. A table renders drag handles only when onReordered is given, allows swipe-to-delete only when onDeleted is given, and shows the add action only when addLabel is set, which in turn needs onAdd or onSaved to act on. Previously drag handles and the add action rendered unconditionally and a swipe was always armed, even with no callback to receive it
    • Migration: a table that should stay reorderable or deletable must pass those callbacks explicitly

โœจ New #

  • CoreSizesTableData โ€” one titled table: id, title, columns, rows, optional addLabel / editLabel / dragHandleLabel, and optional onAdd, onSaved, onDeleted, onReordered
    • id is a stable, locale-independent identity that must be unique among sibling tables. It keys the table's widget so state follows the table rather than its position when the list changes, and is deliberately separate from the display strings: two tables can legitimately share column headers (a rates and a waste table both showing Per unit), and a title changes whenever the result it interpolates does
  • Row actions: a table with onSaved renders a pencil on every row and one with onDeleted renders a trash button, matching the detail-panel design. The pencil opens the same pre-filled entry sheet the row tap already opened; the trash calls onDeleted directly, as the swipe does
    • editRowSemanticsLabelBuilder / deleteRowSemanticsLabelBuilder build each button's label from its row, so a screen reader hears which row it acts on rather than ten identical 'Edit's. Required alongside their callbacks
    • Each button is a 48 dp tap target around a 20 px icon, clearing androidTapTargetGuideline, and claims horizontal drags that start on it so a swipe beginning on a button cannot delete by gesture
    • A table rendering both reserves 96 dp of row width, mirrored in the header. Wide tables scroll horizontally sooner: the four-column fixture now exceeds a 412 dp surface where it previously fit
  • CoreSizesColumn โ€” one column of a table; currently its header title
  • CoreSizesTableData.onAdd โ€” when provided, the app owns the add flow and the built-in SizeEntryBottomSheet is not opened

๐Ÿงช Tests #

  • Widget coverage for independent per-table callbacks: swiping a row in a table without onDeleted deletes nothing, while the deletable table still reports its id
  • Coverage for each affordance disappearing with its callback โ€” hidden drag handles, hidden add action
  • Each user-facing label is asserted alongside the callback that makes it reachable, so a nullable label cannot silently ship an unlabelled drag handle or a titleless entry sheet
  • Golden and a11y fixtures moved onto shared table builders; the drag and delete goldens now pass the callbacks their affordances require

0.22.0 Stable test keys on calculator keys, strip chips and dependent-key pills #

โœจ Features #

  • CoreKeyboard: every key carries a stable Key for Patrol and widget tests. Digits, operators, units and controls take calc_key_<enum name> (calc_key_seven, calc_key_add, calc_key_feet, calc_key_clearAll) from the new DigitTypeX.testKey, OperatorTypeX.testKey, UnitTypeX.testKey and ControlActionX.testKey; the result button carries CoreResultButton.testKey (calc_key_result). The key sits on the rendered button inside each Core*Button, so a button built on its own carries it too (CA-1044)
  • KeyType.testKey (optional) and KeyType.resolvedTestKey: a function-key tile carries testKey, or calc_key_<id> (calc_key_Length) โ€” on the strip and in the "View all" sheet alike
  • SuggestionData.testKey (optional): a strip chip carries it, or the row's default โ€” CoreSuggestionArea.chipTestKey(index) (calc_strip_chip_0) on the primary row and the toggle layout's single row, CoreSuggestionArea.conversionChipTestKey(index) (calc_strip_conversion_0) on the two-row layout's conversions row, so the rows never share a key. Element identity is unchanged: the label / value / unit / kind / index key that keeps a chip's tap highlight bound to its data now sits on a KeyedSubtree around the chip
  • CoreDependentKeyData.testKey (optional): a pill carries it, or CoreDisplayArea.dependentKeyTestKey(index) (calc_dep_pill_0)
  • Display area showcase: the Rate, Waste, O.C and Shown-as pills carry calc_dep_pill_rate / _waste / _oc / _shown_as

No behaviour or layout change: keys only.

๐Ÿงช Tests #

  • Keyboard: every digit, operator, control, unit (imperial and metric) and the result button is found by its key, a function key by resolvedTestKey with testKey winning over the id default, and a tap through the key fires the callback; a tile on its own and the "View all" sheet's tiles carry the same keys; the enum keys and resolvedTestKey are unit-tested
  • Suggestion area: chips take the index default per row, the two-row conversions row its own prefix and the toggle layout's conversions list the single-row prefix; testKey overrides; a tap through the key accepts the suggestion; duplicates still get distinct keys
  • Display area: pills take the index default; testKey overrides and a tap through it fires onPressed
  • Goldens unchanged

0.21.0 Calculator a11y: live regions and dependent-key pill hints #

โœจ Features #

  • CoreSuggestionArea: the area is a live region. Its semantics node is labelled with the suggestions on screen โ€” the active list in toggle, both rows in twoRows minus the conversions row while secondRowHidden โ€” so a screen reader announces a new rung or a fresh set of conversions without moving focus; each chip keeps its own node inside the region. suggestionsSemanticsLabelBuilder(List<SuggestionData>) (optional) builds that text; CoreSuggestionArea.defaultSuggestionsSemanticsLabel joins each suggestion's semanticsLabel โ€” or label, value and unit โ€” with commas (Area: 220 ftยฒ, Cost: $84.25). The placeholder is a live region too, so an emptied strip is heard as well (CA-1043)
  • CoreDisplayArea: the value text is a live region โ€” a computed result, a typed value or the errorTitle is announced when it changes. CoreDependentKeyData.semanticsHint is announced after a pill's label and says what a tap does (Edits the rate, Changes how the pitch is shown), the spoken counterpart of the trailing โœŽ / โ‡„ icon; no default, in line with the row holding no strings of its own
  • CoreButton: semanticsHint passes through to the button's semantics node
  • Display area showcase: the Rate, Waste, O.C and Shown-as pills carry hints

๐Ÿงช Tests #

  • Suggestion area a11y: the region carries the live-region flag and the joined chip text; the text follows a suggestion change, the toggle's active list and secondRowHidden; the builder overrides it; the placeholder is a live region; the existing guideline tests run against the new tree
  • Display area a11y: the value node is a live region whose label follows the value, and the error title, on the same node; pills announce their hint
  • Button: semanticsHint reaches the semantics node

0.20.0 CoreKeyboard group swipe and CoreFunctionKeyBottomSheet reorder callback #

โœจ Features #

  • CoreKeyboard: a horizontal swipe on the function-key strip selects the previous (swipe right) or next (swipe left) group in allGroups through the existing onGroupSelected, wrapping at either end. One gesture selects exactly one group; a drag shorter than CoreKeyboard.groupSwipeThreshold (space16, 64 dp) is ignored, and a tap on a key never counts as a swipe โ€” a swipe that starts on a key cancels that key's tap instead. The "View all" sheet stays the non-gesture equivalent (CA-1038)
  • CoreKeyboard: onGroupsReordered and reorderSemanticsLabelBuilder pass through to the built-in "View all" sheet. The keyboard keeps a rebuild hook rather than an order, so when the consumer applies a reorder โ€” as a new allGroups list or in place โ€” the sheet that is still open re-renders in the new order. Both indices reported by the callback are in range for allGroups
  • CoreFunctionKeyBottomSheet: onGroupsReordered(int oldIndex, int newIndex) reports a drag once the group is dropped; newIndex is already the final index, so groups.insert(newIndex, groups.removeAt(oldIndex)) applies it. The sheet no longer keeps a private copy of the order โ€” it renders groups as given, so the stored preference is the single source of truth. Drag handles render only when the callback is set, so a read-only sheet offers no gesture it cannot honour
  • CoreFunctionKeyBottomSheet: reorderSemanticsLabelBuilder(groupLabel) replaces the hard-coded drag-handle label; defaultReorderSemanticsLabel keeps the previous English string when the builder is omitted
  • Showcases: the keyboard sheet applies reorders to its group list; the display-area and suggestion-area calculators now track the swiped group and apply reorders, so the strip follows the gesture

โš ๏ธ Behaviour change #

  • CoreFunctionKeyBottomSheet without onGroupsReordered shows no drag handles and cannot be reordered. Previously the handles were always shown and dragging reordered a private copy that no consumer could read back โ€” a reorder that was lost on the next rebuild. Wire the callback to keep the handles

๐Ÿงช Tests #

  • Keyboard: swipe left / right select the neighbouring group exactly once, wrap at both ends, a key tap never swipes, a swipe that starts on a key cancels the tap and the key's action, a sub-threshold drag is ignored, a single group ignores swipes; the "View all" sheet forwards the reorder and the handle label and re-renders in the consumer's new order while open
  • Sheet: the drop reports (oldIndex, finalIndex) and the rendered order stays the consumer's; a host that applies the callback renders the new order; no handles without the callback; the handle label defaults to the previous string and follows the builder
  • Goldens: the sheet golden wires the callback so the handles stay and the image is byte-identical; keyboard goldens unchanged

0.19.0 CoreDisplayArea dependent-key row #

โœจ Features #

  • CoreDisplayArea: dependentKeys: List<CoreDependentKeyData> renders a row of pills under the value instead of the single dependentKeyLabel / dependentKeyValue pair, because an answer can depend on more than one assumption at once โ€” a cost shows Rate and Waste together (CA-1037)
    • CoreDependentKeyData { label, value, kind, onPressed, semanticsLabel } with CoreDependentKeyKind { editable, toggle, offer }: editable opens an editor for an assumption and carries the โœŽ icon; toggle respells the value on screen (Shown as: in/12in) and carries the new โ‡„ CoreIcons.swapHorizontal icon; offer is a one-time rewrite (Re-input 38.30ยฐ as 38ยฐ30โ€ฒ) with no icon and a space instead of a colon, so it reads as a sentence
    • The row is end-aligned and scrolls horizontally with the trailing pill anchored in view when the pills outgrow the width; pills are separated by space2
    • Each pill is a CoreButton exposing button: true with its label (or the consumer's semanticsLabel), drawn with a 1 px lineMid hairline rather than the secondary button's 2 px outline, as in the Figma Dependent Key Chip spec (66225:151236); the row holds no default strings, in line with the 0.15.0 localization rule
    • resolvedDependentKeys (@visibleForTesting) exposes the list build renders, so tests assert the adapter without reaching into the widget tree
  • CoreIcons.swapHorizontal (Icons.swap_horiz) added for the toggle pill
  • CoreButton: optional borderColor and borderWidth override the variant's border in every state (null keeps the variant's own), plus CoreButton.hairlineBorderWidth (1 px) for chip-style edges such as the dependent-key pill
  • Display area showcase: a Cost key prices the current Area and shows Rate + Waste editable pills that recompute the cost on tap; the Pitch result carries a Shown as toggle that cycles in/12in โ†’ degrees โ†’ grade

๐Ÿ”ง Fixes #

  • CoreButton: a raised secondary button (variant: secondary with shadows) painted its card buttonInverse โ€” white โ€” in the dark theme too, so the dependent-key pill's textBody / textDark text was near-invisible on it (contrast 1.47:1). In dark mode the card now takes the same elevated backgroundGrayLight surface the social variant already uses; the light theme is untouched. Surfaced by the new pill contrast test; the old single pill had the same defect

๐Ÿ”ง Deprecations #

  • CoreDisplayArea: dependentKeyLabel, dependentKeyValue and onPressedDependentKey are deprecated. They still render โ€” as one editable pill appended after dependentKeys โ€” so existing callers get a deprecation warning only; the adapter is removed in the next minor release

๐Ÿงช Tests #

  • Widget tests: the row renders every pill with its label and value; kind-specific trailing icons (โœŽ / โ‡„ / none) and offer punctuation; per-pill onPressed; button semantics with the default and the overridden label; a disabled pill without onPressed; the row anchors its trailing pill in view and scrolls the leading pills in; the adapter appends the legacy pill and resolvedDependentKeys reflects both sources; the value section shows for pills alone
  • A11y: pills meet label and contrast guidelines in light and dark; each kind is announced with its own label
  • Goldens: display_area_dependent_keys_{light,dark}.png (cost result with Rate + Waste, a Shown as toggle and an offer overflowing the width), viewport scoped to the collapsed display area. The existing dependent-key goldens (more_than_two_rows, expansion stages) migrated to dependentKeys and are byte-identical

0.18.0 CoreSuggestionArea two-row layout #

โœจ Features #

  • CoreSuggestionArea: new layout parameter โ€” CoreSuggestionLayout { toggle, twoRows }, default toggle so existing callers compile and render unchanged (CA-1035)
    • twoRows shows both lists at once: aiSuggestions on row 1 (the rung that fired), conversionSuggestions on row 2, no AI / conversion toggle. Each row keeps its own +N overflow chip and expands on its own; a single non-empty list renders as a single row rather than an empty shelf. This is the calculator's default (prototype strip: 'tworow'); the toggle layout survives behind the app's "Strip layout" preference
    • secondRowHidden (default false) folds the conversions row away so the display area's dependent-key band can take the space. The fold is an AnimatedSize over the new public CoreSuggestionArea.animationDuration (300 ms โ€” the display area's stage timing, so the two surfaces move together); a hidden row is collapsed if it was expanded, and with only conversions present the placeholder shows. Ignored in toggle
    • onExpandedChanged reports true while either row is expanded and false once both are collapsed; a suggestion or layout change collapses both rows, as before
    • conversionsExpandToggleSemanticsLabelBuilder / conversionsCollapseToggleSemanticsLabel (optional) give the conversions row its own overflow semantics labels so a screen-reader user can tell the two rows' +N controls apart; they fall back to the shared labels
    • the conversions row is visibly secondary, as in the calculator prototype's two-row strip: a leading tag (CoreIcons.ruler + conversionsRowTagLabel, default 'as', decorative) says "conversion" once, and every chip on the row is a value-only CoreChipSize.mini โ€” as 264in 7.33yd under Area: 410.67ftยฒ Cost: $84.25. The row is a semantics container labelled conversionsRowSemanticsLabel (default 'Convert to other units'); both strings are overridable per locale. The toggle layout keeps full-size labelled conversion chips
  • CoreChip: gains CoreChipSize.mini โ€” the large chip's page-background surface and lineMid outline at the medium chip's padding, no shadow, value and unit in bodyMediumSemiBold instead of the heavy unit. CoreChipTheme.onPageSurface(size) names the large/mini surface rule, and the chip's text styles now resolve through CoreChipTheme.labelStyle / valueStyle / unitStyle (unitFontWeight = w800) so a size can vary them
  • Suggestion area showcase gains a "Two rows" switch and a "Hide conversions row" switch above the strip; two rows is the showcase default. Chip showcase gains a mini chips row

๐Ÿงช Tests #

  • Widget tests: default layout is toggle; two rows render both lists with no toggle and the conversions row below the primary row; single-list two-row renders one row; secondRowHidden folds the row away and back, animates over the shared duration rather than snapping, shows the placeholder when only conversions exist, and is ignored in toggle; independent per-row overflow with onExpandedChanged aggregation; a suggestion change or a runtime layout change collapses both rows; hiding the conversions row while it is expanded reports collapsed and brings it back collapsed, and reports nothing while the primary row is still open; the conversions row falls back to the shared overflow labels
  • Widget tests: the conversions row renders one tag then value-only mini chips below the full-size row, conversionsRowTagLabel is configurable, and the toggle layout keeps full-size labelled conversion chips
  • A11y: both rows meet tap-target, label and contrast guidelines in light and dark; no toggle is announced in two-row mode; each row announces its own overflow controls; the conversions row announces its group label (configurable) and not the decorative tag, and a value-only chip still announces its value and unit
  • CoreChip: mini renders at the medium height; theme tests for the mini padding, surface, outline, focus fill and semibold value/unit against the heavy unit of the other sizes, in light and dark
  • Goldens: suggestion_area_two_rows_{light,dark}.png (deterministic + predictive over an as tag and three mini conversions), viewport scoped to the two rows; core_chip_outline_{light,dark}.png gains a solid mini chip; every other suggestion-area golden verified byte-identical

0.17.0 CoreSuggestionArea suggestion kinds, bind styling, localisable toggle label #

โš ๏ธ Breaking changes #

  • CoreSuggestionArea: toggleSemanticsLabel is now a required parameter. The AI / conversion toggle's screen-reader label ('Toggle suggestion mode') was the last hard-coded semantics string in suggestion_area/; like the sibling expandToggleSemanticsLabelBuilder and collapseToggleSemanticsLabel it has no English default, so a user-facing string cannot reach the screen without passing through the consuming app's localization layer (CA-1036)
    • Migration: toggleSemanticsLabel: AppLocalizations.of(context).toggleSuggestionMode

โœจ Features #

  • SuggestionData: gains kind โ€” SuggestionKind { deterministic, predictive, bind, conversion, memory }, default predictive โ€” so the app can attach the right accept behaviour without re-deriving it from label text, and an optional semanticsLabel that overrides the chip's announced text ('12.57ydยฒ' โ†’ "Convert to 12.57 square yards"). A suggestion update that only swaps a kind or semanticsLabel now also collapses an expanded area (CA-1036)
  • CoreSuggestionArea: a SuggestionKind.bind offer renders with the dashed offer outline and a trailing bindSuffix (default '?', overridable per locale) appended to its last text segment โ€” Height: 8ft ? โ€” because accepting a bind relabels an existing chip instead of adding a result, and the look says so. The looks follow the Figma Suggestion Strip Chip spec (66225:151222): a deterministic rung renders with the 2 px lineHighlight outline, a memory recall with a leading CoreIcons.history icon (an empty label shows the value alone), and the bind chip keeps the strip's plain fill
  • CoreChip: gains outline (CoreChipOutline { solid, dashed, highlight }, default solid) and semanticsLabel. The dashed outline reuses CoreDashedBorderDecoration (0.16.0) as the chip's foregroundDecoration over the chip's usual fill, with the solid border painted transparent so the chip measures the same and the stroke following the focus border width; CoreChipTheme.dashedOutline(outline:, isFocused:, colors:) resolves it. The highlight outline is a solid lineHighlight border at the focus width (CoreChipTheme.borderWidthFor(outline:)), with the padding giving the extra width back so the chip measures the same
  • Suggestion area showcase: digits typed with no function key start an unnamed entry, and the strip offers bind chips for the dimensions still missing (prototype off-script rule); Area suggestions are tagged deterministic, conversions conversion with spoken semantics labels

๐Ÿงช Tests #

  • Suggestion area widget tests: default kind, bind outline + suffix (value and unit placement, custom suffix), solid kinds unchanged, bind accept callback, semanticsLabel override, custom toggle label, and kind-only change collapsing an expanded area; a11y tests for the bind chip's tap target, label, contrast and announced text in both themes
  • CoreChip widget tests: default solid outline, dashed and highlight chip text, semanticsLabel override, and theme resolution for the dashed chip's unchanged fill and transparent border, the highlight border colour, width and state priority, and the focus stroke width in light and dark
  • Suggestion area widget tests: deterministic renders the highlight outline; memory renders the history icon and hides an empty label
  • Goldens: suggestion_area_bind_{light,dark}.png (bind offer beside a deterministic chip) and core_chip_outline_{light,dark}.png (highlight, solid and dashed at large, dashed at medium), viewport scoped to one chip row; existing suggestion area and chip goldens are byte-identical

0.16.0 CoreCalculatorChip result, dashed and error variants + long-press #

โœจ Features #

  • CoreCalculatorChip: three new CoreCalculatorChipType variants for the calculator tape, so the app no longer has to borrow disabled for an answer or hand-build a chip for an error (CA-1034)
    • result โ€” filled chip for an answer the app computed (prototype: outlined = typed, filled = computed). Shares the muted grey pair of disabled by design (prototype .t-result) but stays interactive so a long-press can open provenance
    • dashed โ€” dashed outlineFocus outline over backgroundBlueLight for a bind offer ("Height: 8ft ?") or a chip being edited in place; text and factor keep the editable teal
    • error โ€” alertRed fill inside a new alertRedOutline stroke (red200 light / red700 dark, the Figma spec's error border) with a regular-weight textDark value for the dimension-error chip that backspace repairs
    • editable, dashed and error carry CoreShadows.small as in the Figma Calculator Chip spec (58781:24269); the filled disabled, active and result chips stay flat
    • onLongPress fires for every variant except disabled; longPressSemanticLabel is exposed as the semantics long-press hint only while the callback is set, so screen readers never announce an action that is not there
    • CoreCalculatorChipTheme.dashedOutline(type:, colors:) resolves the dashed decoration (null for every other type); the solid border is painted transparent at the same width so all six variants measure the same
  • CoreDashedBorderDecoration: new shared Decoration for dashed rounded outlines, applied as a container's foregroundDecoration so the solid BoxDecoration border stays untouched
  • AppColorsExtension: new alertRedOutline token (red200 light / red700 dark) for the stroke around an alertRed surface
  • Calculator chip showcase regrouped by tape meaning (typed / computed / tentative / error) with a long-press provenance demo

๐Ÿงช Tests #

  • Widget tests: tap and long-press gating per variant, long-press semantics action + hint (present with the callback, withheld without it and when disabled), dashed outline resolved only for dashed, and token resolution for the three new variants in light and dark; text contrast checked for the new variants in both themes
  • Decoration unit tests for equality, step interpolation and painting
  • Goldens: the single light golden is replaced by light + dark goldens covering all six variants

0.15.0 Localization ownership moves to the consumer #

โš ๏ธ Breaking changes #

  • KeyType / GroupNameType: both gain a required id โ€” a stable, locale-independent identifier separate from the displayed label. GroupNameType equality and hashCode now key on id alone, so a group stays the same group (and the same Map key) when the app switches locale and re-renders its label. KeyType.groupName is documented as holding the group's id (CA-898)
    • onKeyTapped is unchanged: it already hands over the whole KeyType, so consumers read key.id for domain logic and key.label only for display
    • Migration: pass id at every KeyType / GroupNameType call site. Using the existing English label as the id keeps current domain matching working with no other change
    • GroupNameType.id must be non-empty and unique among sibling groups โ€” equality depends on nothing else, so a shared id collapses two groups into one Map key. The constructor asserts against the empty string, the shape a missed migration takes
  • CoreDisplayArea: closeSemanticLabel and historyPlaceholder are now required. The English defaults ('Close', 'Here will show what you type') and the defaultCloseSemanticLabel / defaultHistoryPlaceholder constants that exposed them are gone, so a user-facing string can no longer reach the screen without passing through the consuming app's localization layer (CA-654)
    • Migration: pass localized strings at every call site, e.g. closeSemanticLabel: AppLocalizations.of(context).closeButton. Callers that relied on the constants for test assertions should assert against their own localized value instead

๐Ÿงช Tests #

  • Display-area widget, golden, and a11y call sites updated to pass both strings explicitly; goldens are byte-identical since the default text is unchanged
  • GroupNameType identity tests: equal across differing labels, unequal across differing ids, still resolving as a Map key when the label is localized, and an empty id rejected at construction
  • KeyType identity test: id is independent of the displayed label

0.14.1 Dark-theme colour audit: switch contrast, tooltip theming, AppColorsExtension dedup #

๐Ÿ”ง Fixes #

  • CoreSwitch: the normal (non-error) inactive thumb fill moves from lineDarkOutline to iconGrayMid so it clears WCAG 1.4.11 (3:1 non-text contrast) against the track in both CoreTheme.light() and CoreTheme.dark(); the error-state thumb is unchanged (F10 in the dark-theme colour audit)
    • _getInactiveThumbColor now delegates to _getBorderColor instead of duplicating its body
  • CoreTooltip: theme-dependent colours and typography are captured in _showTooltip() from the widget's declaring context and threaded into the overlay, instead of being re-resolved against the root navigator's overlay context. A tooltip inside a locally themed subtree (e.g. a Theme(data: CoreTheme.dark()) wrapper under a light MaterialApp) now renders with its local theme. This matches Flutter's own Tooltip, which also resolves theme values at show time (F7 in the dark-theme colour audit)

๐Ÿ”ง Internal #

  • AppColorsExtension: create() / createDark() now delegate to CoreTheme.lightAppColors() / CoreTheme.darkAppColors() instead of holding a second copy of the token map. Output is unchanged (F11 in the dark-theme colour audit)

๐Ÿงช Tests #

  • test/theme/theme_extensions_test.dart pins AppColorsExtension.create() / createDark() field-for-field against CoreTheme.lightAppColors() / darkAppColors(), and asserts the dark factory returns the dark palette rather than the light one
  • Switch goldens: a dark golden is added (switch_component_dark.png) and the light golden is refreshed for the new inactive-thumb colour
  • CoreTooltip gains a regression test for the locally-themed-subtree case

0.14.0 CoreDivider hairline rule #

โœจ Features #

  • CoreDivider: new 1px hairline rule that replaces the hand-tokened Material Divider call sites in the consuming app (the search-results end-of-results footer and the auth pages' "or" separators), which each re-applied thickness: 1 + lineLight with private constants (CA-1016)
    • Exactly CoreDivider.thickness (1px) tall with no built-in whitespace โ€” unlike Material's Divider and its default 16px height, vertical rhythm stays at the call site as CoreSpacing tokens; in a Row via Expanded the rule adds no vertical extent, so the label-separator row is sized by the text alone
    • Color defaults to the theme extension's lineLight, so the rule tracks CoreTheme.light() and CoreTheme.dark(); color overrides it for surfaces that need a different line token
    • Every Material Divider parameter is pinned โ€” including radius: BorderRadius.zero โ€” so a consuming app's ambient DividerThemeData cannot restyle the rule
    • indent / endIndent inset the rule from either edge; pass CoreSpacing tokens
    • resolvedColor(context) (@visibleForTesting) exposes the color build paints, so tests assert color resolution without reaching into the widget tree
    • Purely decorative: exposes no semantic node, matching Material's Divider
    • Defaults are derived from the two consumer call-site families, not measured from Figma directly; CA-1016 names the pagination-footer frame (65869:151824) as the design source for review cross-checking
  • Divider showcase screen added to the example catalogue (full-bleed, inset, custom color, label separator, end-of-list footer)

๐Ÿงช Tests #

  • Widget tests pin the 1px-tall/full-width geometry, the text-only row height and centering in the label-separator Row, and color resolution across both themes plus the explicit override
  • A11y test pins the purely-decorative contract โ€” no announceable semantics node โ€” in light and dark
  • Goldens for the three rule variants (full-bleed, inset, lineMid override), light + dark

0.13.1 CoreSearchBox exposes test keys on the inner text field and clear button #

Version note: 0.13.1 is a deliberate patch even though the change is a Feature โ€” it is additive-only, and 0.14.0 is already claimed by the open CA-898 (#158) and CA-654 (#157) branches. Whichever of #157/#158/#159 merges last reconciles the version headers.

โœจ Features #

  • CoreSearchBox: exposes CoreSearchBox.textFieldKey (core_search_box_text_field) on the inner text field and promotes the existing clear-button key to CoreSearchBox.clearButtonKey (core_search_box_clear_button, string unchanged), so app widget tests can target both with find.byKey instead of fragile find.byType(TextFormField) descendant finders. Both keys are shared statics, matching CoreInputChip.removeButtonKey โ€” scope with find.descendant when a screen renders more than one search box (CA-952)

๐Ÿงช Tests #

  • Widget tests pin both key strings, assert the keyed widget is the single rendered text field, and pin the shared-static behavior across two instances; the suite migrated to the shared buildTestApp harness with CoreTheme.light() and every finder now goes through the key constants

0.13.0 CoreDateFilterChip active pill reuses the CoreInputChip primitive #

โœจ Features #

  • CoreInputChip: adds removeOnChipTap (default false) โ€” when true, tapping anywhere on the chip invokes onRemove and the whole chip is exposed as a single semantic button labeled with removeSemanticLabel; the close (ร—) icon stays visible as the removal affordance but is no longer a separate tap target (CA-830)

๐Ÿ”ง Changes #

  • CoreDateFilterChip: the active pill is now a CoreInputChip with whole-chip tap-to-remove instead of a hand-built container, so it adopts the chip family's visual treatment (pill radius, chipGrey background, semibold label, size-20 close icon). Consumers with goldens of the active pill will see pixel drift and should regenerate (CA-830)

๐Ÿงช Tests #

  • Unit + semantics tests for the whole-chip tap-to-remove mode (tap anywhere removes, single button node, icon stays, no-op without onRemove); default-mode chip goldens are byte-identical
  • CoreDateFilterChip active-pill goldens regenerated (light + dark)

0.12.0 CoreAppBar #

โœจ Features #

  • CoreAppBar: new top app bar that implements PreferredSizeWidget, so it drops straight into Scaffold.appBar (CA-823)
    • Separating shadow comes from CoreShadows.medium via BoxDecoration, with Material elevation held at zero, so the shadow is drawn exactly once instead of doubling
    • CoreAppBarElevation { none, shadow, material } covers the un-shadowed bar, the CoreShadows bar, and surfaces that must match a Material-elevated sibling
    • padding is additive to preferredSize (preferredSize.height == height + padding.vertical), so padding never shrinks the content box. This is the failure mode behind the 48x40 tap target in CA-822; the constructor also asserts height >= CoreSpacing.space12 (48) so leading and action tap targets can always meet the 48x48 guideline
    • height defaults to CoreSpacing.space14 (56) โ€” measured from the consuming app, where 56 is the preferred size of 9 of the 12 existing bars (HeaderRow uses 64; the two estimation bars use an off-grid kToolbarHeight + 5). The class doc carries a caveat that Figma's reusable "Action Bar" component instead measures 64 total with t8/b8/l4/r16 baked-in padding, so CA-823 migration sites should pass height/padding explicitly rather than treating the code-derived default as spec-confirmed
    • decorationShadow (@visibleForTesting) exposes the shadow the bar's decoration paints, resolved from elevation and consumed by build itself, so tests assert elevation behavior without reaching into the widget tree
    • scrolledUnderElevation is held at zero in every mode, so the bar does not darken or re-tint when content scrolls under it
    • Accepts an arbitrary title widget (custom rows, icon clusters) or a titleText convenience styled titleMediumSemiBold in textHeadline; supplying both asserts
    • Colors resolve from the theme extension (pageBackground, textHeadline, iconDark), so the bar tracks CoreTheme.light() and CoreTheme.dark()
    • implyLeading defaults to false, so the bar never sprouts a Material back button just because the route is poppable โ€” the app bar design has no back button. leading is rendered independently of the flag, so an explicit close/back icon is never silently dropped
    • Holds no user-visible strings โ€” leading and actions pass their own semanticLabel through, keeping localization in the consuming app

๐Ÿงช Tests #

  • Widget tests: preferred-size arithmetic, both asserts, elevation modes, theming fallback and override, action rendering and callbacks, and leading behaviour over a real pushed route (no implied back button by default, opt-in via implyLeading, explicit leading rendered regardless)
  • Golden tests: five bar shapes (flat/no-shadow, custom title row, back button with project title, Material elevation, plain title) in both light and dark, with the viewport scoped to each bar's own preferredSize so every golden contains exactly the bar and no empty body space
  • A11y tests: tap-target and label guidelines in both themes, including at the minimum permitted height
  • Title contrast is asserted from the resolved tokens rather than sampled pixels; the pixel-sampling guideline reads the AppBar title's antialiased glyph edges and reports a blend of text and background rather than the token colors

0.11.2 Keep CoreMultiSelectSheet visible above the keyboard #

๐Ÿ”ง Fixes #

  • CoreMultiSelectSheet: the sheet now pads itself by the keyboard's view inset and lets the item list shrink, so the search field, list, and action buttons stay visible above the keyboard while the user types (CA-842)

๐Ÿงช Tests #

  • Widget test: presents the sheet through CoreQuickSheet.show (the real presentation path), simulates the keyboard opening, and asserts the search field, list items, and Apply button all sit above the keyboard
  • Golden tests: keyboard-open sheet in both light and dark themes

0.11.1 CoreBottomNavBar action button semantic label #

๐Ÿ”ง Fixes #

  • CoreBottomNavBar: adds actionButtonSemanticLabel parameter โ€” when provided, the trailing circular action button is wrapped in a Semantics node so screen readers can announce it; when null (default) behavior is unchanged (backward compatible, no golden change)

๐Ÿงช Tests #

  • Semantics test: verifies label and isButton flag appear on the trailing button's semantics node
  • A11y test: confirms the labeled trailing button meets tap-target and label guidelines in both light and dark themes

0.11.0 Parameterize CoreBottomNavBar for 2โ€“4 tabs #

โœจ Features #

  • CoreBottomNavBar: now accepts 2โ€“4 tabs (previously required exactly 4)
    • Assert updated to tabs.length >= 2 && tabs.length <= 4
    • Layout computation derives tab-row and nav-bar base widths dynamically from tabs.length, so pill, active-tab, and inactive-tab proportions are correct for any supported tab count
    • 2-tab design verified against Figma spec (CA-874)
    • Inactive tab icons corrected from iconGrayMid to iconWhite for contrast on dark track
    • Active tab label uses textLink token (semantic fix; same hex value in all themes)
    • Existing 4-tab layout unchanged; goldens regenerated for icon color fix

๐Ÿงช Tests #

  • Boundary assert tests: rejects < 2 tabs and > 4 tabs
  • 2-tab rendering tests: active label only visible, correct icon count
  • 2-tab interaction test: tap second tab fires onTabSelected(1)
  • New golden: core_bottom_nav_bar_2tab_default.png

0.10.2 Accessibility #

โœจ Features #

  • CoreInputChip: add optional removeSemanticLabel for a localizable remove-button announcement; when null, keeps the default 'Remove <label>' English label

0.10.1 Dark-mode contrast fixes #

๐Ÿ”ง Fixes #

  • Accessibility / Dark mode
    • CoreButton (social variant): background changed from buttonInverse (gray25 โ€” near-white) to backgroundSecondaryDark in dark mode, preventing invisible content when text and icon tokens also resolve to near-white
    • DimensionCard: same background-swap fix applied; card surface is now backgroundSecondaryDark in dark mode instead of buttonInverse
    • SizeCard: same background-swap fix applied; card surface is now backgroundSecondaryDark in dark mode instead of buttonInverse
    • All three fixes mirror the existing CoreSelectButton dark-mode guard pattern; contrast ratios now meet WCAG AA (โ‰ฅ 4.5:1 for text, โ‰ฅ 3:1 for UI components)

๐Ÿงช Tests #

  • Social button: WCAG contrast a11y test + light & dark golden tests
  • DimensionCard / SizeCard: WCAG contrast a11y tests added to core_geometry_area_a11y_test.dart
  • Dark-mode golden tests added for CoreGeometryArea (collapsed and expanded)

0.10.0 Search & Filter Components #

โœจ Features #

  • UI Components
    • CoreDateFilterChip: Filter chip for a date-range filter. With no selection it renders a plain CoreFilterChip that opens a CoreDateRangeSheet on tap; with a selection it renders an active pill showing the formatted range with a clear ร—. Surface-agnostic: each caller supplies its own label, accessibility labels, and widget keys.
    • CoreDateRangeSheet: Modal bottom sheet for picking an inclusive, whole-calendar-day DateRange. Offers predefined ranges (Today, Last 7 days, Last 30 days, This month) plus a Custom range option that opens CoreDatePicker twice โ€” once for the start date, once for the end date. Resolves with the chosen DateRange, or null on cancel/dismiss.
    • CoreMultiSelectSheet: Modal bottom sheet body for selecting multiple values from a searchable list of {id, label} items. The caller supplies the (already filtered) list and reacts to search and apply callbacks; present it with CoreQuickSheet.show.
    • DateRange: Value type representing an inclusive calendar-day range, shared by the date filter components.
    • All three components ship with showcase screens, widget tests, accessibility tests, and light + dark golden tests.

0.9.1 Dart 3.8 compatibility patch #

๐Ÿ”ง Fixes #

  • Dependency constraints loosened for Dart 3.8 compatibility
    • flutter_svg: ^2.3.0 โ†’ ^2.2.3 โ€” 2.3.0 requires Dart โ‰ฅ3.9.0; 2.2.3 is the last release compatible with Dart 3.8. No coreui APIs from 2.3.0 are used.
    • lottie: ^3.4.0 โ†’ ^3.3.1 โ€” same reason; only Lottie.asset() with stable params is used.
    • ripplearc_linter moved from dependencies to dev_dependencies โ€” the linter has no runtime role and should never have been a transitive dependency for consumers; this was causing analyzer ^8.4.0 to cascade to every app using coreui, breaking build tooling on Dart 3.8.

0.9.0 Dark theme #

โœจ Features #

  • Dark Color Tokens
    • 9 dark token classes mirroring each light class (DarkBackgroundColors, DarkTextColors, DarkIconColors, DarkBorderColors, DarkTabColors, DarkButtonColors, DarkInputColors, DarkSelectColors, DarkStateColors) โ€” all colors sourced from the Figma dark-mode palette
    • CoreTheme.dark() now returns a fully populated ThemeData with brightness: Brightness.dark and scaffoldBackgroundColor mapped to gray50; both AppColorsExtension and AppTypographyExtension are switched to their dark variants automatically
    • AppTypographyExtension.createDark() โ€” all 19 text styles substituted with CoreDarkTextColors.* (gray25 for headlines, gray100 for titles, gray300 for body); components using typography.someStyle without .copyWith now render correctly in dark mode

๐Ÿ”ง Fixes #

  • Accessibility
    • SingleItemSelector modal title: uses .copyWith(color: colors.textHeadline) so text stays visible on the dark scaffold (was gray900 on gray900 โ€” 1:1 contrast)
    • SingleItemSelector item text: uses .copyWith(color: colors.textBody) to ensure list items remain legible in dark mode
    • CoreSelectButton selected tab: text color switches to textInverse (gray900) when tab background is tabsHighlight (orient300), resolving the 1.6:1 contrast failure in dark mode
  • CoreLetterAvatar: replaced Image.asset with a BoxDecoration-based Container wrapped in AspectRatio(aspectRatio: 1.0); fixes Semantics label propagation that was blocked by Image.asset and correctly derives height from the available width constraint without a RenderBox infinite-constraint error

Tests #

  • CoreDatePicker Visual Regression - Dark golden added โ€” verifies header background (blue900), selected day fill (orient200), and month row text under CoreTheme.dark()
  • Dark-mode goldens added for color tokens, letter avatar, and check row item; all light goldens refreshed against current Flutter SDK

0.8.0 CoreInputChip #

โœจ Features #

  • UI Components
    • CoreInputChip: New non-toggleable input chip for displaying committed tokens (e.g. email addresses or tags) with a remove button.
      • Displays a text label in bodyMediumSemiBold with TextOverflow.ellipsis โ€” safe inside Wrap rows and on narrow screens
      • Trailing close (ร—) button meets the 48 dp minimum tap-target requirement; tapping calls onRemove
      • onRemove is optional โ€” omitting it hides the remove button entirely, enabling a read-only/locked-token display mode
      • Full accessibility support: chip container exposes a Semantics(container: true) node with the label text; remove button exposes a Semantics(button: true) node labelled "Remove <label>"; label Text is wrapped in ExcludeSemantics to prevent double-announcement
      • CoreInputChip.removeButtonKey static key for locating the tap target in tests
      • Widget tests, accessibility tests (both themes), and golden tests (light + dark, short label + email label)

0.7.2 CoreCheckRowItem & CoreDatePicker #

Upgraded #

  • Flutter SDK bumped from 3.32.0 to 3.44.4; Dart SDK constraint raised to >=3.12.0 <4.0.0.
  • Gradle wrapper 8.13 โ†’ 8.14.
  • Android Gradle Plugin (AGP) 8.7.0 โ†’ 8.11.1.
  • Kotlin Gradle Plugin 2.1.0 โ†’ 2.2.20.
  • flutter_lints ^5.0.0 โ†’ ^6.0.0.
  • flutter_svg ^2.2.2 โ†’ ^2.3.0, lottie ^3.3.1 โ†’ ^3.4.0, ripplearc_linter ^0.4.0 โ†’ ^0.4.1.
  • Minimum supported iOS deployment target raised from 12.0 to 13.0 (example app).

Fixed #

  • Fixed a drag-reorder regression in CoreFunctionKeyBottomSheet where migrating to Flutter's new onReorderItem callback (which now performs index correction internally) had left the widget's own manual index-correction logic in place, causing dropped items to land one position off from where the user released them.

Changed #

  • Migrated ReorderableListView/ReorderableListView.builder usages (_SizesTable, CoreFunctionKeyBottomSheet) from the deprecated onReorder callback to onReorderItem, ahead of Flutter's planned removal of onReorder.
  • Migrated widget tests off the deprecated SemanticsNode.hasFlag/SemanticsData.flags API to the new flagsCollection API, including the isSelected/isEnabled flags moving from bool to the new Tristate enum.
  • SingleItemSelector's bottom sheet item now wraps its ListTile in a Material widget with Clip.antiAlias, fixing the tap ripple/ink effect rendering outside the intended bounds.
  • CoreKeyboard's reveal/collapse SizeTransition migrated from axisAlignment: -1.0 to alignment: AlignmentDirectional.topStart.

Tests #

  • Existing SingleItemSelector widget tests now pass without framework exceptions after the Material(clipBehavior: Clip.antiAlias) wrapper fix.

0.7.0 CoreCheckRowItem & CoreDatePicker #

โœจ Features #

  • UI Components
    • CoreCheckRowItem: New selectable list row โ€” leading widget, title (+ optional subtitle), and a trailing checkbox.
      • Whole row is tappable; tapping toggles selected via onChanged
      • Defaults the leading widget to a 24ร—24 circle showing the first initial of title (derived from the first whitespace-delimited token, uppercased, e.g. "John Doe" โ†’ "J"; blank title renders an empty circle, no crash); avatarBackgroundColor/avatarTextColor/avatarTextStyle theme it (ignored when a custom leading is supplied); avatarTextColor is applied last and remains the single source of truth for the glyph colour
      • Trailing checkbox swaps between CoreIcons.check and CoreIcons.checkBlank based on selected
      • Optional subtitle for a second line (e.g. an email address)
      • Localizable semanticLabel param (defaults to title); exposed as a Semantics(button: true, checked: selected) node
    • CoreDatePicker: New modal calendar widget for picking a single date (CA-220).
      • Header with a localizable label and a large spelled-out selected date ("Mon, Aug 17"-style by default, fully overridable via dateLabelBuilder)
      • Month selector row with previous/next navigation; arrows disable themselves once an adjacent month would be entirely out of the optional firstDate/lastDate range
      • Day grid with selected (filled), "today" (outlined), and disabled (out-of-range) states
      • CoreDatePicker.show static helper presents the picker in a themed dialog and resolves with the confirmed DateTime, or null on cancel/dismiss
      • monthLabelBuilder and weekdayLabels allow full localization of all date text without subclassing
      • Each day cell exposes a Semantics(button: true, selected: ...) node with a full date label via MaterialLocalizations.formatFullDate

0.5.0 Search components #

โœจ Features #

  • UI Components
    • CoreSearchBox: New borderless search input field.
      • Built-in leading search icon and auto-appearing clear button (shown only when the field has text)
      • Flat appearance with no visible border โ€” designed for global or in-page search bars
      • Accepts an optional TextEditingController and FocusNode; manages its own when none are supplied
      • onChanged, onSearch (keyboard submit), and onClear callbacks
      • enabled flag renders the field non-interactive with a backgroundGrayMid fill
      • clearSemanticLabel localizable constructor param (defaults to 'Clear search')
      • hintText localizable constructor param for placeholder text
    • CoreSearchRowItem: New single-row item for search screens.
      • Two named constructors: CoreSearchRowItem.recentSearch (history icon) and CoreSearchRowItem.suggestion (search icon with bold-prefix query highlighting)
      • Trailing โ†— icon with independent onTrailingTap callback (e.g. fill the search field without triggering a search)
      • showTrailingIcon flag to hide the trailing icon
      • semanticLabel and trailingSemanticLabel localizable params for full screen-reader support
      • Custom variant via the default constructor: caller supplies any leadingIcon and a pre-built label widget

0.4.1 CoreIconSize token #

โœจ Features #

  • Design Tokens
    • CoreIconSize: New icon size token with four canonical sizes โ€” size16 (16dp), size20 (20dp), size24 (24dp), size32 (32dp).
      • Value-based naming reflects how icon sizes are referenced in design tooling and specs
      • Exported from the public barrel alongside other theme tokens
      • Golden test verifying each size using CoreIconWidget

0.4.0 CoreFilterChip component #

โœจ Features #

  • UI Components
    • CoreFilterChip: New dropdown-style filter chip for filter rows.
      • Filled pill design using backgroundGrayMid (#F2F4F7) background token
      • Trailing dropdown arrow icon in iconDark (#015B7C) color
      • label (required) and onTap (optional) public API โ€” chip is non-interactive when onTap is null
      • Full accessibility support: outer Semantics node exposes label and button role (only when enabled); Text and arrow icon wrapped in ExcludeSemantics to prevent double-announcement
      • Widget tests, accessibility tests, and golden tests (enabled, long label, disabled states)

0.3.9 CoreToast title support #

โœจ Features #

  • UI Components
    • CoreToast: Added optional title parameter to showSuccess, showError, and showWarning methods.

๐Ÿ”ง Fixes #

  • Code Quality
    • Improved null safety in CoreToast descriptions to avoid displaying "null" strings.
    • Cleaned up redundant documentation and implementation comments.

0.3.8 CoreQuickSheet component #

โœจ Features #

  • UI Components
    • CoreQuickSheet: New standardized bottom sheet component for consistent sheet presentation across the app
      • Automatic content-based height (up to 90% of screen)
      • Custom drag handle with consistent styling
      • Theme-aware background color (defaults to pageBackground)
      • Configurable dismiss behavior (isDismissible, enableDrag)
      • Optional safe area handling (useSafeArea)
      • Optional custom background color override
      • Rounded top corners (28px) per design spec
      • Returns values when dismissed for result handling

๐Ÿ”ง Fixes #

  • Code Quality
    • Fixed tooltip component forced unwrapping issue with overlay entry
    • Improved null safety in tooltip overlay insertion

0.3.7 Add splash screen icons #

โœจ Features #

  • Icons
    • Added splash screen animation icons (splashFirstState, splashSecondState, splashThirdState)
    • New SVG icons available via CoreIcons for splash screen animations

0.3.6 Accessibility improvements #

โœจ Features #

  • Accessibility
    • Added accessibility tests for all interactive components (CoreAvatar, CoreLetterAvatar, CoreKeyboard, CoreButton, CoreBottomNavBar, CoreLoadingIndicator)
    • Tests verify tap target size, semantic labels, and text contrast guidelines

๐Ÿ”ง Fixes #

  • Design Tokens

    • Updated text link color from orient600 to orient800 to match UI design specification
  • Accessibility

    • Fixed CoreButton text overflow with ellipsis and FittedBox scaling for long labels
    • Fixed accessibility-related contrast and layout issues across components

0.3.5 Code quality improvements #

โœจ Features #

  • UI Components

    • CoreLoadingIndicator: Added Lottie-based loading indicator component with customizable size and fit options
  • Dependencies

    • Added lottie (^3.2.0) for animation support
  • Assets

    • Added loading animation asset (assets/animations/loading.json)

0.3.4 Code quality improvements #

๐Ÿ”ง Fixes #

  • Code Quality
    • Fixed avoid_static_colors linter violations
    • Integrated shadow colors into theme system for consistent design token usage

0.3.3 Theme extension naming consistency #

โš ๏ธ Breaking Changes #

  • TypographyExtension has been renamed to AppTypographyExtension for consistency with other theme extensions
  • Update your code: Theme.of(context).extension<TypographyExtension>() โ†’ Theme.of(context).extension<AppTypographyExtension>()

0.3.2 Code quality improvements #

๐Ÿ”ง Fixes #

  • Code Quality
    • Fixed avoid_static_typography linter violations
    • Fixed forbid_forced_unwrapping linter violations
    • Fixed specific_exceptions_types linter violations

0.3.1 Add transparent utility color #

โœจ Features #

  • Design Tokens
    • Added transparent utility color to the core color palette and AppColorsExtension for consistent use across apps.

0.1.0 Initial Release #

โœจ Features #

  • UI Components

    • CoreBottomNavBar: A customizable bottom navigation bar component with responsive sizing and smooth animations.
    • SuccessModal: A bottom sheet that is displayed to the user when an operation is successful.
    • Toast: Provides a static interface to display toast messages, e.g., Toast.showSuccess, Toast.showError, Toast.showWarning.
    • CoreButton: Customizable button with support for primary, secondary, and social variants, multiple sizes, icons, and disabled state.
    • CoreTextField: Flexible text input with label, helper text, error handling, phone number input, prefix/suffix widgets, and country code selector.
    • SingleItemSelector: Single-select dropdown with bottom sheet support.
    • CoreIconWidget: Unified icon widget supporting both Material and SVG icons.
  • Design Tokens

    • Color tokens (brand, gray, blue, red, etc.)
    • Typography tokens (font sizes, weights, styles)
    • Spacing tokens (consistent spacing system)
    • Shadow tokens (multiple shadow levels)
    • Icon tokens (Material and custom SVG icons)
  • Theming

    • Light and dark theme support
    • Easily extendable theme data for custom branding
  • Assets

    • Extensive icon set (SVG and Material icons)
    • IBM Plex Sans Hebrew font family included
3
likes
0
points
1.89k
downloads

Publisher

verified publisherripplearc.com

Weekly Downloads

A Flutter design system package with design tokens and basic components.

Homepage
Repository (GitHub)
View/report issues

License

unknown (license)

Dependencies

flutter, flutter_svg, lottie

More

Packages that depend on ripplearc_coreui