fix: move createSingleSelectionContext(multiple) out of the $effect()…#1878
fix: move createSingleSelectionContext(multiple) out of the $effect()…#1878shinokada merged 1 commit intothemesberg:mainfrom
Conversation
… and call it synchronously during component initialization
|
@shinokada is attempting to deploy a commit to the Themesberg Team on Vercel. A member of the Team first needs to authorize it. |
WalkthroughA change to Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~5 minutes
Possibly related PRs
Poem
Pre-merge checks and finishing touches✅ Passed checks (3 passed)
✨ Finishing touches
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
fix: #1876
📑 Description
Move createSingleSelectionContext(multiple) out of the $effect() and call it synchronously during component initialization
This ensures that each Accordion creates its own isolated selection context, even when nested inside other components like Tabs
A change to src/lib/accordion/Accordion.svelte that replaces an asynchronous reactive effect with a synchronous call to createSingleSelectionContext(multiple) during component initialization, affecting initialization order and ensuring the selection context is created immediately.
🔍 PR Type
🚦 PR Status
✅ Checklist
pnpm lint && pnpm check && pnpm test:e2eand all tests passmainbranch (not the published npm version)🧪 Screenshots / Demos (optional)
ℹ️ Additional Information
Summary by CodeRabbit
✏️ Tip: You can customize this high-level summary in your review settings.