FE-674: Suppress no-op Undo on hard apply + V3.0 polish#118
FE-674: Suppress no-op Undo on hard apply + V3.0 polish#118kostandinang wants to merge 2 commits into
Conversation
54006af to
aff3024
Compare
d225815 to
33ce6e0
Compare
33ce6e0 to
9464e9f
Compare
aff3024 to
ead1ecf
Compare
PR SummaryMedium Risk Overview Polishes hard-impact apply behavior by tagging hard edit applies as Updates design docs ( Reviewed by Cursor Bugbot for commit d2a3611. Bugbot is set up for automated code reviews on this repo. Configure here. |
🤖 Augment PR SummarySummary: This PR finishes the V3.0 polish pass by extracting the cascade “Pending review” UI, tightening resolve/fixture tests, and hiding Undo for hard-only applies where undo is a no-op. Changes:
Technical Notes: The UI now composes three independent sticky regions (staged changes, pending review, saved toast), and the “Undo” surface is suppressed specifically for hard-only batches where undo cannot reverse the source mutation. 🤖 Was this summary useful? React with 👍 or 👎 |
9464e9f to
f74f37c
Compare
ead1ecf to
b1542b0
Compare
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit f74f37c. Configure here.
b1542b0 to
ec73476
Compare
f74f37c to
37085de
Compare
ec73476 to
0fe4440
Compare
41359bd to
675db5b
Compare
0fe4440 to
4f63bdd
Compare
4f63bdd to
cb5c12b
Compare
675db5b to
bfeff81
Compare
…assertions) Squashed from six commits: - Reconcile SIDE_CHAT.md §5.3 with §9 V3.0 single-Resolve action - Extract <PendingReviewSection> from patch-list-overlay - Move makeNeed test helper to shared fixture - Add F5 network-call-counter assertions to Resolve action - Add 5+-downstream / all-relations fixture for hard cascade - Suppress Undo for hard-only batches; close polish refactor
The savedToast was being suppressed when an undoable batch was followed by a hard-only batch: canUndo transitioned true→false in the same render that lastBatchId changed, so the canUndo cleanup effect cleared the toast right after the lastBatchId effect set it. Track previous canUndo via a ref and only hide when canUndo specifically transitioned from true to false — the actual signal we want (the user undid).
bfeff81 to
d2a3611
Compare
cb5c12b to
308215b
Compare


What
Six small polish commits over the V3.0 stack from a code-review pass.
Stacked on #117.
Changes
SIDE_CHAT.md§5.3 now agrees with §9 that V3.0 has one Resolve action.<PendingReviewSection>out ofpatch-list-overlay.tsx— overlay becomes pure layout. Focused tests follow.makeNeedfixture across overlay + section tests.Test plan