Search blocks by description or jump to a page.
Draft comments held for one review, each with a section anchor, quote, and edit controls, above a summary field, verdict choices, and a submit button.
The source for every Application block is included with Pro and Team. Start a plan to copy the code.
Already on a plan? Log in
Pending Review Tray batches draft comments so nothing publishes one at a time: four drafts on Payments API spec v2, each showing its section anchor (2.1 Authentication, 3.4 Error envelope, 4.2 Pagination, 6.0 Webhooks), the quoted passage in a muted italic line, and edit and discard controls. Below the list sits a review summary field prefilled with the reviewer note, a verdict choice of Comment, Approve, or Request changes locked on Request changes, and a submit action that publishes the batch.
Drafts are one typed array; verdicts are a separate const. The header count, the draft badge, and the submit line all read four, so the copy stays in sync with the data. The footer note is the honest promise: drafts stay on the document until you submit or discard them, and leaving the page keeps the batch intact rather than losing your work.
Reach for this block as the batched review step of any document or design tool, wired to your draft-comment store and a publish mutation. Bind Submit review to the call that posts every draft at once and records the chosen verdict.
A natural flow around it on an Application Pro page:
Before
After
One strong use is the spec review tray above. Other pending batch shapes:
Tip: the footer note, drafts stay until you submit or discard, is what makes the batch feel safe to leave and come back to later.