Repository navigation
fix: recover failed deck renames - #925
Conversation
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configuration
You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Outcome
Failed deck renames restore the prior displayed name when the attempted name is still current and show a retry notification. A different newer name remains untouched. Deleted decks are not recreated or warned about. English user guide updated.
TDD
Observed focused Red in store-core.test.ts: expected Test Deck, received New Name. Updated the existing test that characterized the unwanted behavior, then implemented minimal rollback. Supplementary passing characterization covers retry feedback, a different newer successful name, and deletion during the pending rename. Broader concurrent rename ordering, repeated identical names and confirmed-baseline recovery remain open; no general serialization claimed.
VPS validation
3,050 tests across 274 files passed; TypeScript, lint, production build and diff checks passed. Full blocking Docker Playwright: 66 passed in isolated Compose, with server diagnostic logging, unchanged exclusions and no retries or bypass. Prior intermittent test-server issue remains documented and is not claimed fixed. Sonar attempted locally: configuration absent; CI advisory result will be recorded before merge. Dedicated roadmap/changelog/progress documentation follows merge into dev.