Search blocks by description or jump to a page.
Pending edit review rows showing the struck original beside the proposed replacement with author attribution and accept and reject actions per suggestion.
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
Suggestion Review Row is the pending-edits queue for the Acme API reference: three rows from Jordan Lee, Maya Chen, and Priya Nair, each showing the original text struck through above the proposed replacement. Jordan wants the vague encoding sentence replaced with a concrete UTF-8 JSON instruction. Each row names the section (Overview / paragraph 2, Rate limits / note, Errors / 429 description), and every footer states the honest rule: rejecting keeps the original and lets you send a reason to the suggester.
Suggestions are one typed array with a status const. The diff surface uses a muted background block rather than red and green fills, keeping the block on theme tokens throughout. Accept all and Reject all in the panel header handle the bulk action.
Reach for this block on any document edit-review screen, wired to your suggestion model and patch mutation. Accept should apply the diff to the document immediately and log it in history; Reject should notify the author.
A natural flow around it on an Application Pro page:
Before
After
One strong use is the API documentation suggestion queue. Other suggestion review shapes:
Tip: the honest footer note, rejecting notifies the suggester, is the line that turns a quiet button into a legible workflow contract.