@snacky/ui 0.10.0 → 0.12.0

package/CHANGELOG.md

@@ -4,6 +4,67 @@ How `@snacky/ui` got to its current state. The README documents what the
 package *is*; this documents how it got there, including the mistakes, so the
 verification claims in the README can be taken at face value.
 
+## The solid address icon (0.12.0)
+
+`SnackyIcons.solid.address` is new: the filled map marker, added to Figma's
+`Icon-solid` set as `general/pin` (UIcons `fi-sr-marker`), 16x16, with its fill
+bound to `icon/icon-brand`. The solid set is 13 icons now.
+
+It ships as `address` rather than `pin` because a solid icon here takes the name
+of its outline twin, and this is the same marker shape as the existing
+`SnackyIcons.outline.address`. That is the rule the rest of the set already
+follows (Figma's `riwayat` is `history`, `Fav` is `heart`), and it means an
+active/inactive pair is always `outline.x` and `solid.x` with no lookup table.
+It is 16px where its outline twin is 24; `heart` has the same kind of mismatch
+(20 solid, 24 outline), and each icon still defaults to its own authored size.
+
+compose-ui ships the same icon as `SnackyIcons.Solid.Address` in
+`compose-v2.2.0`, plus one helper it was missing:
+`SnackyTypographyToken.toTextStyle(color, fontFamily)`. compose-ui's type tokens
+are raw values rather than `TextStyle`s (the package ships no font), and nothing
+turned one into the other, so every component built the style by hand and 58 of
+the docs site's Kotlin samples could not compile: 24 called a `toTextStyle()`
+that did not exist, and the rest used flat names like
+`SnackyTypography.smallRegular` that never did either. Those samples now use
+`SnackyTypography.Small.regular.toTextStyle()`. The React samples had the same
+flat-name problem (`typography.smallRegular`, 43 places) against an export that
+is nested (`typography.small.regular`), and are fixed the same way. Additive on
+both sides.
+
+## PageIndicator, and a semantic role for indicator dots (0.11.0)
+
+`PageIndicator` is the dot row under a carousel: 8x8 dots, a 28x8 pill for the
+current page, `gap/cell` apart, so the row stays 8 tall whichever page is
+showing. It reports position rather than changing it, so the dots are
+`aria-hidden` with no click target and the row carries a single label ("Page 2
+of 3" by default). Make the carousel itself operable and let this follow it.
+
+The component is small; the reason it exists is the two tokens under it.
+`--bg-indicator-active` and `--bg-indicator-inactive` are new semantic roles,
+referencing `--color-amber-500` and `--color-neutral-200`. Adding a role rather
+than reusing one needs a reason, and there were two. Figma drew the dots as raw
+hex, one of them `#dadada`, a grey in no ramp at all. And `Stepper` was already
+borrowing: its done dot painted `--icon-brand`, an icon token used as a shape
+fill, and its pending dot `--bg-action-disabled`, which says a step the order
+has not reached yet is a control you cannot use. Two components needing
+"reached" versus "not yet", both saying something false, is what a missing role
+looks like. Stepper now uses the pair, and its rendered colours are unchanged
+(`#f8b732` and `#cccccc`, exactly as before).
+
+Worth knowing if you theme the system: `--bg-indicator-inactive` and
+`--bg-action-disabled` resolve to the same grey today but are free to diverge,
+which is the point. Override the indicator one to restyle carousels and
+progress dots without touching disabled controls.
+
+compose-ui ships the same as `compose-v2.1.0`: `SnackyPageIndicator`, the
+`SnackyColor.bgIndicatorActive`/`bgIndicatorInactive` pair, and the same Stepper
+change. Both are additive, so neither release breaks anything.
+
+Two README corrections came along: compose-ui still claimed
+`SnackyPointBalanceBanner` paints the `primary-500` primitive, which stopped
+being true when its binding was fixed against Figma in 0.10.0, and both READMEs
+still counted 11 solid icons rather than 12.
+
 ## Brand ramp renamed to amber, components re-checked against Figma (0.10.0)
 
 **Breaking: the brand primitive ramp is now `amber`.** It was the only

package/README.md

@@ -121,19 +121,20 @@ placeholder artwork rather than a real icon prop. Apply your own
 
 ## What's here
 
-All 24 documented components, matching the real Figma-sourced spec values
+All 25 documented components, matching the real Figma-sourced spec values
 (padding, colors, radius, states - all sourced directly from the design
 tokens, not eyeballed):
 
 Button, IconButton/UploadButton, Input family (TextField, SearchField,
 OtpField, CopyField, ChatInput, AddressResult), Chips (ProductChip/FilterChip),
-RadioOption, Checkbox, Toggle, NavBar, TabRow, Header, Banner family, Badge family,
+RadioOption, Checkbox, Toggle, NavBar, TabRow, Header, PageIndicator, Banner
+family, Badge family,
 Callout, List (OrderListItem/NotificationListItem), Accordion, BottomSheet
 (the shared Modal shell), Section (the shared content-block shell), Avatar,
 Illustration, ProductImage, ProductCard.
 
 Plus the icon set, as `SnackyIcons.outline.*` and `SnackyIcons.solid.*` (42
-Outline, 11 Solid). Two things to know: they are **filled** shapes rather than
+Outline, 13 Solid). Two things to know: they are **filled** shapes rather than
 stroked paths, so there is no `strokeWidth` to set, and the set is **not
 uniform** - each icon is authored at 16, 20 or 24px and defaults to its own
 natural size, so pass `width`/`height` if you need them to match.