fix: Settings ignores an endpoint check once the same "Save" is tapped again (closes #698) #699

Merged
clawbot merged 1 commits from issue-698-latest-save-wins into next 2026-11-02 22:59:23 +01:00
1 Commits
Author SHA1 Message Date
sneak 1e7e6cb3ef fix: Settings ignores an endpoint check once the same "Save" is tapped again (closes #698)
check / check (push) Canceled after 0s
e2e / e2e-chrome (push) Canceled after 0s
e2e / e2e-firefox (push) Canceled after 0s
Each RPC and Blockscout "Save" in Settings now counts its taps. A check
that answers after a newer tap of the same "Save" stores nothing and
leaves the flash message alone. Before this change, the older check's
error or refusal replaced the newer tap's "Saved.".

The save also checks for a newer tap at two points. A tap made while the
save waits for the lock means nothing is stored. A tap made during the
write means no flash message is shown.

Model: opus-5-5
2026-11-02 21:32:31 +00:00