docs: prefer Drive handles across adapter heroes and guides#25
Conversation
Align Drive examples (`useLayer` / `injectLayer` / `createLayer`) with home snippets and package README taste; bag-form remains a valid escape hatch.
🦋 Changeset detectedLatest commit: 1e24ab3 The changes in this PR will be included in the next version bump. This PR includes changesets to release 2 packages
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 |
|
Warning Review limit reached
Next review available in: 1 minute Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the 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 configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (19)
✨ 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 |
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.
Summary
useLayer/injectLayer/createLayer) instead of bag-formclient.open({ …opts, payload }), matching home snippets and package README taste.awaiting-results,getting-started,error-handling,payload-validation,singletons,identity-and-types,overview,when-to-use. Bag-form stays a documented escape hatch (migration).docs/roadmap.md(done here).@stainless-code/vue-layers+@stainless-code/svelte-layers(shipped skills).Test plan
.open(payload)createLayer; bag-form sections still present where neededconfirm.openblume checkgreendocslabel deploys/layers