humanspeak / svelte-motion / 29040897708

60%

main: 57%

push

github

feat(svg): bind MotionValues to SVG attributes, add attrX/attrY/attrScale (#441)

* docs(plans): guard log for 002 red-test checkpoint

Verdict DRIFTING: e2e asserts on getAttribute('cx'), but svgEffect
style-routes cx/r/stroke-dashoffset (verified in Chromium). Plan defect
on the camelCase attribute allowlist.

* test(svg): add red tests for MotionValue-driven SVG attributes

Guard snapshot of plan 002 before implementation lands. Committed with
--no-verify by operator authorization: the pre-commit svelte-check fails
by design on a test-first commit (helpers not yet exported from svg.ts).

- Unit: SVG_ATTRIBUTE_PROPERTIES classification, resolveSVGAttrKey,
  extractSVGMotionValueAttributes, computeSSRSVGAttrValues
- e2e: no [object Object] in DOM or SSR payload, bound-channel updates,
  attrX/attrY/attrScale rendering

Known-red and under revision: three e2e tests assert on getAttribute()
for style-routed keys (cx/r/stroke-dashoffset). See the guard log.

Refs #435

* docs(plans): amend 002 for svgEffect's two DOM channels

svgEffect routes MotionValue-bound props by `key in element.style`:
cx/cy/r/x/y/width/height/d and stroke-*/`*Opacity` are CSS properties in
Chromium and are written to element.style; only points/viewBox/x1..y2 and
attrX/attrY/attrScale reach setAttribute. The plan implied one attribute
channel, which produced e2e tests that poll getAttribute('cx') and can
never go green.

- Allowlist must carry kebab-case DOM spellings (Svelte, not JSX)
- Don't rename attr* on the MotionValue side; svgEffect converts it
- SSR must emit DOM attribute names or the value flashes on hydration
- e2e asserts the bound channel; parseFloat on computed styles
- Re-stamp `Planned at` to af90f5a; README 002 -> IN PROGRESS

No done criterion weakened. Refs #435

* docs(plans): preserve the SVG channel probe behind 002's amendment

svgEffect picks its write channel with `key in element.style`, which is a
property of the target browser, not of this repo. This ... (continued)

864 of 1661 branches covered (52.02%)

Branch coverage included in aggregate %.

39 of 46 new or added lines in 2 files covered. (84.78%)

3332 of 5331 relevant lines covered (62.5%)

24.11 hits per line