Skip to content

docs: prefer Drive handles across adapter heroes and guides#25

Merged
SutuSebastian merged 3 commits into
mainfrom
docs/prefer-wired-handles
Jul 18, 2026
Merged

docs: prefer Drive handles across adapter heroes and guides#25
SutuSebastian merged 3 commits into
mainfrom
docs/prefer-wired-handles

Conversation

@SutuSebastian

@SutuSebastian SutuSebastian commented Jul 18, 2026

Copy link
Copy Markdown
Contributor

Summary

  • Adapter Confirm heroes (react/preact/solid/vue/angular/svelte) open via Drive handles (useLayer / injectLayer / createLayer) instead of bag-form client.open({ …opts, payload }), matching home snippets and package README taste.
  • Guides + concepts flipped Drive-first: awaiting-results, getting-started, error-handling, payload-validation, singletons, identity-and-types, overview, when-to-use. Bag-form stays a documented escape hatch (migration).
  • Vue/Svelte skill fire-and-forget examples + Batteries card updated the same way.
  • Plan retired; optional pedagogy bullet removed from docs/roadmap.md (done here).
  • Patch changeset for @stainless-code/vue-layers + @stainless-code/svelte-layers (shipped skills).

Test plan

  • Spot-check adapter Confirm sections show handle .open(payload)
  • Guides lead with handle / createLayer; bag-form sections still present where needed
  • Batteries “Await a result” card cites wired confirm.open
  • blume check green
  • Merge with docs label deploys /layers
  • Changeset present for vue/svelte patch

Align Drive examples (`useLayer` / `injectLayer` / `createLayer`) with
home snippets and package README taste; bag-form remains a valid escape hatch.
@SutuSebastian SutuSebastian added the docs Merged PRs with this label deploy the /layers docs site label Jul 18, 2026
@changeset-bot

changeset-bot Bot commented Jul 18, 2026

Copy link
Copy Markdown

🦋 Changeset detected

Latest commit: 1e24ab3

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 2 packages
Name Type
@stainless-code/vue-layers Patch
@stainless-code/svelte-layers Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

@coderabbitai

coderabbitai Bot commented Jul 18, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@SutuSebastian, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 1 minute

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 98b2df18-e96f-4fae-8795-4449415f33cd

📥 Commits

Reviewing files that changed from the base of the PR and between 80ed7cf and 1e24ab3.

📒 Files selected for processing (19)
  • .changeset/prefer-wired-handles.md
  • apps/docs/content/adapters/angular.mdx
  • apps/docs/content/adapters/preact.mdx
  • apps/docs/content/adapters/react.mdx
  • apps/docs/content/adapters/solid.mdx
  • apps/docs/content/adapters/svelte/runes.mdx
  • apps/docs/content/adapters/svelte/store.mdx
  • apps/docs/content/adapters/vue.mdx
  • apps/docs/content/concepts/identity-and-types.mdx
  • apps/docs/content/concepts/overview.mdx
  • apps/docs/content/concepts/when-to-use.mdx
  • apps/docs/content/guides/awaiting-results.mdx
  • apps/docs/content/guides/error-handling.mdx
  • apps/docs/content/guides/getting-started.mdx
  • apps/docs/content/guides/payload-validation.mdx
  • apps/docs/content/guides/singletons.mdx
  • apps/docs/pages/_home/Batteries.astro
  • packages/svelte/skills/svelte-layers/SKILL.md
  • packages/vue/skills/vue-layers/SKILL.md
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch docs/prefer-wired-handles

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

Lift optional Drive-first guide pedagogy to roadmap; decision already lives in migration.
Flip awaiting-results, getting-started, error-handling, payload-validation,
singletons, and related concepts to wired-handle / createLayer first; keep
bag-form as an explicit escape hatch. Drop the roadmap pedagogy bullet.
@SutuSebastian SutuSebastian changed the title docs: prefer wired handles in adapter Confirm heroes docs: prefer Drive handles across adapter heroes and guides Jul 18, 2026
@SutuSebastian
SutuSebastian merged commit ae949d2 into main Jul 18, 2026
17 checks passed
@SutuSebastian
SutuSebastian deleted the docs/prefer-wired-handles branch July 18, 2026 09:25
@github-actions github-actions Bot mentioned this pull request Jul 18, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

docs Merged PRs with this label deploy the /layers docs site

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant