Repository navigation
fix(plugin-detail): a record on a print page does not print its approval band (objectui#12751) - #12785
Merged
objectstack-fleet[bot] merged 3 commits intoOct 16, 2026
Conversation
…val band (objectui#12751) DetailView reads the print context once, above every early return, and does not draw the approval band (recall button, status badge, tally) on a page that declares print. Off a print page the band is unchanged. Co-authored-by: Claude <noreply@anthropic.com>
…double (objectui#12751) Co-authored-by: Claude <noreply@anthropic.com>
…int-approval-strip
Contributor
✅ Console Performance Budget
The eager closure is every chunk the entry reaches through static imports — what the browser fetches and parses before the app renders. The entry chunk on its own is a small fraction of it. 📦 Bundle Size Report
Size Limits
|
Contributor
Author
席位核对 · ACCEPT ·
|
objectstack-fleet
Bot
deleted the
claude/issue-12751-print-approval-strip
branch
October 16, 2026 20:55
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.
Fixes #12751
Clause-②: no
What
On a page that declares
print, a record in approval no longer prints its approval band. The "Recall approval" button, the "In approval · editable" / "Locked for approval" status badge and the "Approvals — 0 of 1" tally do not reach paper. Off a print page the band is unchanged.packages/plugin-detail/src/DetailView.tsxnow readsusePrintPage()once, above every early return (isPrintPage), the wayDetailSectionreads it since PR #12729. The approval band's condition gains&& !isPrintPage, so on a print page none of the band is drawn: the badge, the recall button, the tally, the per-group ticks and the recall-error line.Why hide the status and the tally, not print them as text
The card leaves this open. The spec answers it:
record:approvalsandrecord:approval_decisionbecause what they show changes per viewer and per decision.record:pathbecause the current stage is a field thatrecord:detailsalready prints.The band's badge is host-threaded per viewer (the approvals read, the submitter signal), and its tally moves with every decision. A printed record that should say it is awaiting approval prints the record's own status field through
record:details. Printing a plain-text badge would add new rendering that nobody has asked for.Tests
DetailView.printApprovalBand-12751.test.tsx:PrintPageProvider, for both an editable and a locking approval: no recall button, norole=status, no progressbar, and the record's field still renders;schema.showHeader === false && (() => {):Tests 2 failed | 2 passed (4). Both print rows went red and both controls stayed green. The file was restored from HEAD; blob 97b55210cfb0 equals HEAD andgit diff HEADis empty.pnpm exec vitest run packages/plugin-detail: 2682 passed, 14 skipped.DetailView: 1784 passed.Local gates
All of these exited 0:
@object-ui/plugin-detail;check:changeset-claims,changeset:check,check:test-path-roots,check:spec-symbolsandcheck:new-line-citations;eslint: 0 errors.
DetailView.tsxhas the same warning count as on main, and the new test file is clean.Printed page
Setup:
@objectstack/*@18.0.0-next.2showcase backend.printpage onshowcase_invoice, added in the scratch copy only.Results:
The PNGs are on branch
claude/issue-12751-evidenceunderevidence/12751/.Acceptance notes
record:detailshides the record's title field because it assumes a page header draws it, and a print page refusespage:header. This is reported for the seat to file.DetailView's own header (showHeader: true) and the auto-tabs strip. They would print their controls if an author enabled them inside a print page. No producer was measured doing so.Provenance: built by the cloud session
session_01F54KeYBZhaNDNQjYZJ3HmP(claim6223385481) and opened by thedomain:uiseat 1 PM (session_011K9g23W67dy2zwnyzaoB6o) from that session's final message, because a cloud session cannot open a PR from its container. The seat made no change to the dev's text and added this line.Generated by Claude Code