feat(studio): surface pending drafts on the package detail (ADR-0033)#1469
Merged
Conversation
Add MetadataClient.listDrafts (GET /api/v1/meta/_drafts) and a "Pending changes" section in the package detail sheet that lists each drafted item with a link to the existing per-item review/publish flow — so an AI-built app package no longer looks empty and the drafts are reachable. Unit tests for the client method (URL + envelope tolerance). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub. |
Contributor
✅ Console Performance Budget
📦 Bundle Size Report
Size Limits
|
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
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.
Context
After an AI builds an app, its objects/views land as drafts bound to the app package, but Studio's active-only browsers hid them — so a just-built package looked empty and there was no obvious path to review/publish. (Companion to framework PR objectstack-ai/framework#1552, which adds the
GET /api/v1/meta/_draftsbackend.)Change
MetadataClient.listDrafts({ packageId?, type? })→ callsGET /api/v1/meta/_drafts, returning pending draft headers (withpackageId). Tolerant of both the bare-array and{data:{drafts}}envelope shapes.PackagesPage) now renders a Pending changes section: a count badge + each drafted item linking to the existing per-item review/diff (?review=1), so the user can publish each. A just-built app package is no longer shown as empty.Verification
app.customer_supportpackage detail shows PENDING CHANGES (5) listing customer/ticket/agent_note/ticket_list/app; clickingcustomeropens the review/diff (confirming_packageId: app.customer_support) with the Publish action.listDraftsrequest URL (packageId + type) and envelope tolerance. data-objectstack metadata-client suite green.🤖 Generated with Claude Code