-
-
Notifications
You must be signed in to change notification settings - Fork 9.8k
Docs: Fix Svelte references #32985
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Docs: Fix Svelte references #32985
Conversation
📝 WalkthroughWalkthroughDocumentation updates adding Svelte CSF code examples, Storybook configuration snippets, and SvelteKit mocking patterns. Replaces inline code examples with external snippet references and updates SvelteKit documentation links to point to current documentation structure. Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes
Possibly related PRs
📜 Recent review detailsConfiguration used: CodeRabbit UI Review profile: CHILL Plan: Pro 📒 Files selected for processing (7)
🧰 Additional context used📓 Path-based instructions (1)docs/**📄 CodeRabbit inference engine (.github/copilot-instructions.md)
Files:
🧠 Learnings (21)📓 Common learnings📚 Learning: 2025-10-13T13:33:14.659ZApplied to files:
📚 Learning: 2025-09-17T08:11:47.197ZApplied to files:
📚 Learning: 2025-11-05T09:38:47.694ZApplied to files:
📚 Learning: 2025-10-13T13:33:14.659ZApplied to files:
📚 Learning: 2025-11-05T09:37:25.903ZApplied to files:
📚 Learning: 2025-10-13T13:33:14.659ZApplied to files:
📚 Learning: 2025-09-17T08:11:47.196ZApplied to files:
📚 Learning: 2025-10-13T13:33:14.659ZApplied to files:
📚 Learning: 2025-09-17T08:11:47.196ZApplied to files:
📚 Learning: 2025-09-17T08:11:47.196ZApplied to files:
📚 Learning: 2025-09-17T08:11:47.196ZApplied to files:
📚 Learning: 2025-09-17T08:11:47.196ZApplied to files:
📚 Learning: 2025-09-17T08:11:47.196ZApplied to files:
📚 Learning: 2025-09-17T08:11:47.196ZApplied to files:
📚 Learning: 2025-09-17T08:11:47.197ZApplied to files:
📚 Learning: 2025-09-17T08:11:47.196ZApplied to files:
📚 Learning: 2025-09-17T08:11:47.196ZApplied to files:
📚 Learning: 2025-09-17T08:11:47.196ZApplied to files:
📚 Learning: 2025-09-17T08:11:47.197ZApplied to files:
📚 Learning: 2025-09-17T08:11:47.197ZApplied to files:
🪛 LanguageTooldocs/_snippets/svelte-framework-options-docgen.md[grammar] ~1-~1: Hier könnte ein Fehler sein. (QB_NEW_DE) ⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (2)
🔇 Additional comments (10)
Comment |
|
View your CI Pipeline Execution ↗ for commit 2a6e675
☁️ Nx Cloud last updated this comment at |
Docs: Fix Svelte references (cherry picked from commit 67db3e4)
Closes #
What I did
With this pull request, the Svelte & SvelteKit framework pages were adjusted to include actual snippets and other minor adjustments to reflect the current state of the documentation.
What was done:
Checklist for Contributors
Testing
The changes in this PR are covered in the following automated tests:
Manual testing
This section is mandatory for all contributions. If you believe no manual test is necessary, please state so explicitly. Thanks!
Documentation
MIGRATION.MD
Checklist for Maintainers
When this PR is ready for testing, make sure to add
ci:normal,ci:mergedorci:dailyGH label to it to run a specific set of sandboxes. The particular set of sandboxes can be found incode/lib/cli-storybook/src/sandbox-templates.tsMake sure this PR contains one of the labels below:
Available labels
bug: Internal changes that fixes incorrect behavior.maintenance: User-facing maintenance tasks.dependencies: Upgrading (sometimes downgrading) dependencies.build: Internal-facing build tooling & test updates. Will not show up in release changelog.cleanup: Minor cleanup style change. Will not show up in release changelog.documentation: Documentation only changes. Will not show up in release changelog.feature request: Introducing a new feature.BREAKING CHANGE: Changes that break compatibility in some way with current major version.other: Changes that don't fit in the above categories.🦋 Canary release
This PR does not have a canary release associated. You can request a canary release of this pull request by mentioning the
@storybookjs/coreteam here.core team members can create a canary release here or locally with
gh workflow run --repo storybookjs/storybook publish.yml --field pr=<PR_NUMBER>Summary by CodeRabbit