-
Notifications
You must be signed in to change notification settings - Fork 13
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
Add Ability to Delete All Saved Passwords #2265
Conversation
… and associated unit tests
…fillActionExecutor
…view model, rename notification
…esign Readiness Review feedback
…management, add scaffolding for alternate text based on Sync being enabled
8a0288e
to
418020e
Compare
@@ -14,8 +14,7 @@ | |||
"kind" : "remoteSourceControl", | |||
"location" : "https://github.com/duckduckgo/BrowserServicesKit", | |||
"state" : { | |||
"revision" : "04c35220aa94bd005171086acccadd677400e7d5", | |||
"version" : "111.0.2" | |||
"revision" : "f087cf8389926b58692870bd5a459bad492ce66d" |
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.
I’ll update this to point to the latest version once the related BSK PR is merged.
@@ -1059,6 +1059,63 @@ struct UserText { | |||
} | |||
} | |||
|
|||
// MARK: Autofill Item Deletion (Autofill -> More Menu, Settings -> Autofill) |
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.
Note: It’s possible copy with change after review.
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.
There is actually a dedicated UserText+PasswordManager.swift
that contains all the autofill related copy; perhaps these strings can be moved there too? 🙂
|
||
var confirmationAlert: NSAlert { | ||
let accounts = (try? secureVault.accounts()) ?? [] | ||
let syncEnabled = syncService.account != nil |
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.
Note: I think on iOS we went with checking if account.authenticated
is true. I’m unsure which is the better check, but we check the accounts object at another point in the macOS codebase.
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.
Good question, in the iOS codebase we're usually using syncService.authState == .inactive
which is what I went with.
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.
Ok, I've checked with Dominik and he says syncService.authState == .inactive
is best to use as:
we have more states between inactive and active and every other than inactive means that sync is enabled or being enabled
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.
Great, thanks @amddg44, I’ll update PR and Ship Review build
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.
LGTM! V nice work @aataraxiaa
…lection after data refresh
Task/Issue URL: https://app.asana.com/0/72649045549333/1206560791755490/f Description: Last remaining translation for Delete All Password feature Additional changes to Russian translations (as requested by @mallexxx)
Task/Issue URL: https://app.asana.com/0/72649045549333/1206560791755490/f
Tech Design URL: NA
CC:
Description:
This PR adds the ability to delete all passwords via a single action. It also includes changes to the Settings screen.
Steps to test this PR:
Delete all
flow but this time lock the macbook at the stage where you are asked to authenticate<!—
Tagging instructions
If this PR isn't ready to be merged for whatever reason it should be marked with the
DO NOT MERGE
label (particularly if it's a draft)If it's pending Product Review/PFR, please add the
Pending Product Review
label.If at any point it isn't actively being worked on/ready for review/otherwise moving forward (besides the above PR/PFR exception) strongly consider closing it (or not opening it in the first place). If you decide not to close it, make sure it's labelled to make it clear the PRs state and comment with more information.
—>
—
Internal references:
Pull Request Review Checklist
Software Engineering Expectations
Technical Design Template
Pull Request Documentation