Split the Motion reference into one page per component - #636
Conversation
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01FVXrJ8idMfvt667yJadvB8
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01FVXrJ8idMfvt667yJadvB8
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01FVXrJ8idMfvt667yJadvB8
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #636 +/- ##
=========================================
Coverage 87.75% 87.75%
Complexity 145 145
=========================================
Files 153 153
Lines 5415 5415
Branches 1030 1030
=========================================
Hits 4752 4752
Misses 579 579
Partials 84 84
Flags with carried forward coverage won't be shown. Click here to find out more.
🚀 New features to boost your workflow:
|
Code ReviewRisk: Low — The reference split and documentation updates are safe to merge; no concrete defects are visible in the supplied diff. The MR separates the Motion reference into four component-specific pages, relocates their examples and stories, and updates catalog, contract, and source documentation links. It also adds ambient MotionView integration stories and removes the duplicated DomUpdate type re-export. Review usage: 201,355 in (174,691 cached) / 1,359 out tokens — $0.0295 (openrouter/openai/gpt-5.6-luna, thinking: low) Reviewed by @weareikko/code-review v0.9.5 for commit a70de5d. |
Export sizeBundled per export with peer dependencies left external, dynamic imports excluded and the output minified; sizes are gzipped. ✅ No export size changes. Unchanged (133)@studiometa/ui
@studiometa/ui-mapbox
@studiometa/ui-motion
|
What
Motionreference item into four items, one page per component:Motion,MotionScrollTimeline,MotionSequenceandMotionView— each with its ownindex.md,js-api.md,examples.mdandstories/(story directories moved withgit mvso history follows). The package-level "Providing the Motion dependency" section stays on theMotionJS API page and every sibling links to it.MotionViewintegrations: a zero-wiring exit animation fordata-bind:ifand ambient view transitions in aDialog.motion-viewtoview-transition/dialog/data-bind), the public contracts (Motion*Propshrefs), the@linkdocblocks inpackages/ui-motion/src, and theMotionViewmentions in the Fetch, DataBind and Dialog JS API pages (including dropping the stale "upcoming").DomUpdateRunner/DomUpdateTransitionertype re-export inpackages/ui/src/index.ts(merge artifact) solint:typespasses again.Test plan
node scripts/validate-reference.ts: passes with 66 Reference entries, 273 symbols and 5 concepts.npm run lint: 0 errors, 20 warnings.npm run build --workspace=@studiometa/ui-motion: passes.npm run test -- -- Motion/: 8 files, 58 tests, all green.data-bind:ifpanel animates in and out, and the dialog opens and closes through the ambient join.🤖 Generated with Claude Code
https://claude.ai/code/session_01FVXrJ8idMfvt667yJadvB8