@snacky/ui 0.7.1 → 0.7.3

package/CHANGELOG.md

@@ -135,3 +135,22 @@ unverified - see the README's Verification status.
   `space-between`) - the original 0.6.2 bug was the groups spreading apart,
   not the fill-width itself, so this keeps that part of the fix while
   dropping the part that looked wrong once seen with real sibling content.
+- **Button's icon slot was disproportionate at Small size (0.7.2).** The slot
+  is documented generically as 24x24, and that was applied uniformly
+  regardless of `size` - reasonable for Default (48px tall, 12px label), but
+  oversized next to Small's 40px height and 12px label. Added a `.snacky-btn--
+  small .snacky-btn__icon` override at 20x20; Default stays 24x24. Ported the
+  same conditional to compose-ui's `SnackyButton`, and to the docs site's own
+  Button playground (previously hardcoded to 24 regardless of the size
+  control). Confirmed via computed styles in the Live Preview iframe, not
+  just visually: the icon span and its inner SVG both resolve to exactly
+  20x20 with Size=Small selected.
+- **That same fix used raw pixel values instead of the existing semantic
+  size tokens (0.7.3).** `tokens.json` already has `size.icon.md` (20px) and
+  `size.icon.lg` (24px), generated as `--size-icon-md`/`--size-icon-lg` in
+  react-ui and `SnackySize.Icon.md`/`.lg` in compose-ui - 0.7.2 hardcoded
+  `20px`/`24px` and `20.dp`/`24.dp` instead of reaching for them, caught right
+  after shipping. Swapped both platforms over to the token references; the
+  computed pixel values are unchanged (re-verified: still exactly 20px at
+  Small, now genuinely resolving through `--size-icon-md` rather than a
+  literal that happens to match it).

package/README.md

@@ -1,8 +1,7 @@
 # @snacky/ui
 
 React implementation of the Snacky App design system - generated from the
-source of truth at `../../index.html` (via `tokens.json` / `components.json`),
-pixel-accurate to Figma.
+source of truth at `../../index.html`, pixel-accurate to Figma.
 
 This exists so AI coding tools (and humans) building new Snacky features can
 **import** these components directly instead of regenerating similar-looking
@@ -122,9 +121,9 @@ placeholder artwork rather than a real icon prop. Apply your own
 
 ## What's here
 
-All 24 documented components, each matching its `code.tsx` sample's prop
-shape from `components.json` (padding, colors, radius, states - all sourced
-directly from the design tokens, not eyeballed):
+All 24 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),
@@ -151,8 +150,8 @@ above) - not one of the 24, there is no Figma node for it.
 
 Every component is diffed against `index.html`'s own Live Preview
 implementation - the code that actually renders the documentation site - not
-just the spec values in `components.json`. Where the two disagree, the
-verified implementation wins.
+just the prose spec values on the page. Where the two disagree, the verified
+implementation wins.
 
 See [CHANGELOG.md](https://github.com/rezatresnas/snacky-design-system/blob/main/packages/react-ui/CHANGELOG.md)
 for how the package got here, including the mistakes.