Add useParams hook - #6
Merged
Merged
Conversation
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
JoviDeCroock
added a commit
that referenced
this pull request
Apr 18, 2026
drizzle-kit's migrate command can't talk to D1 (no TCP endpoint) — the skill previously emitted db:migrate scripts that would silently fail on D1 projects. Split Step 5/6/8/9 by provider: - D1 drizzle.config.ts omits dbCredentials (generate-only), notes d1-http driver for studio. - D1 scripts use wrangler d1 migrations apply, with --local and --remote variants so users can iterate against miniflare before touching prod. - wrangler.toml binding gets migrations_dir matching drizzle's out path. - Added rule #6 spelling out the D1 footgun. Pattern mirrors the working setup in ~/Documents/SideProjects/Sarah/api. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
JoviDeCroock
added a commit
that referenced
this pull request
Apr 18, 2026
* fix(skills): correct accuracy bugs in five SKILL.md files
- audit-shells: ErrorBoundary is a route export, not a shell one; flag it
as misplaced. Document shell headers() export too.
- audit-csrf: remove stray empty ```bash fence.
- tune-render-mode: add Edit to allowed-tools so §Step 4 can apply the
recommended render-mode change.
- add-db: fix Node Postgres example — schema was imported after use.
- add-observability: defineApp({ middleware }) is a name→path registry,
not an ordered chain; document that ordering lives in group/api
middleware arrays.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
* fix(skills): branch add-db migrate workflow for Cloudflare D1
drizzle-kit's migrate command can't talk to D1 (no TCP endpoint) — the
skill previously emitted db:migrate scripts that would silently fail on
D1 projects. Split Step 5/6/8/9 by provider:
- D1 drizzle.config.ts omits dbCredentials (generate-only), notes d1-http
driver for studio.
- D1 scripts use wrangler d1 migrations apply, with --local and --remote
variants so users can iterate against miniflare before touching prod.
- wrangler.toml binding gets migrations_dir matching drizzle's out path.
- Added rule #6 spelling out the D1 footgun.
Pattern mirrors the working setup in ~/Documents/SideProjects/Sarah/api.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
useParams()hook that reads route params from context, eliminating the need to prop-drillparamsfromRouteComponentPropsparamsthroughViactRuntimeProvideron both client (router) and server (SSR) render paths{}as a safe default when used outside a route contextTest plan
useParams()returns correct params on SSR and client navigationuseParams()returns{}outside a route context