-
Notifications
You must be signed in to change notification settings - Fork 1
fix(auth): define reset and delete safety flows #104
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.
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
Closed
Closed
Changes from all commits
Commits
Show all changes
17 commits
Select commit
Hold shift + click to select a range
af7f137
fix(auth): define reset and delete safety flows
ndycode 3ca9da5
fix(auth): refresh working storage after delete
ndycode 8f176b0
fix(auth): keep delete state aligned after reset actions
ndycode 87eace8
Merge remote-tracking branch 'origin/main' into fresh/01-reset-safety
ndycode 291f25f
fix(auth): harden destructive cleanup paths
ndycode 7098a13
fix(storage): handle empty-dir destructive clears
ndycode bac086d
fix(quota-cache): redact clear warnings
ndycode 21583b2
fix(codex-manager): resync after active delete
ndycode 6b36986
fix(auth): preserve deleted account labels
ndycode 5eb23bf
fix(auth): keep delete cleanup best-effort
ndycode d17c65a
test(auth): harden reset safety regressions
ndycode 8a664e0
fix(auth): align quota cleanup safety
ndycode 983eb18
docs(storage): document clear helper return values
ndycode 5d0a17f
fix(auth): keep delete failures inside the menu loop
ndycode b860c23
fix(cli): reuse fallback readline during confirms
ndycode fdc7f20
test(reset): cover mixed destructive action guard
ndycode ad95afa
fix(auth): harden reset and delete failure handling
ndycode File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🧹 Nitpick | 🔵 Trivial
Object.assigncalls are dead code in current control flow.deleteAccountAtIndexpersists changes internally (perlib/destructive-actions.tstwo-phase write). after this block, line 3131 hitscontinue, jumping back to the top of thewhile(true)loop at line 3029 whereworkingStorageandflaggedStorageare reloaded from disk anyway. these assignments update local vars that are immediately discarded.either remove the
Object.assigncalls or, if keeping them for future use (e.g., skipping reload on the next iteration), add a comment explaining why.🧹 suggested cleanup
if (deleted) { - Object.assign(workingStorage, deleted.storage); - Object.assign(flaggedStorage, deleted.flagged); invalidateAccountManagerCache(); const label = deleted.removedAccount.email?.trim() ||🤖 Prompt for AI Agents