Skip to content

Header lifecycle actions succeed and the contract page keeps showing the old status and the old button until a manual reload #105

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
zhuangjianguo merged 1 commit into from
Oct 25, 2026
Merged

Header lifecycle actions succeed and the contract page keeps showing the old status and the old button until a manual reload #105

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 8 additions & 0 deletions src/actions/contract-lifecycle.actions.ts
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -106,6 +106,14 @@ const transition = (
// rendered zero actions on a draft AND on a signing contract.
visible: P`record.status == ${from}`,
...(requiredPermissions ? { requiredPermissions: [...requiredPermissions] } : {}),
// The status this button writes is the status the header shows, and the
// status every one of these `visible` predicates reads. The spec defaults
// `refreshAfter` to `false` (materialized at parse), and the record page
// re-reads the record only when it is `true`. Measured on 17.7.0 (issue
// #94): without it each press answered `200 {"success":true}` and toasted
// success while the header kept the old stage and the old button until a
// manual reload; no `GET` of the record followed the action.
refreshAfter: true,
});

/** 提交 — the requester hands the draft over. No capability gate. What limits
Expand Down
Loading