-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Edit logins - duplicates and save criteria #10173
Comments
Related to #10172 - that PR should be merged before this can be merged. |
Hey @eliserichards how is this going? I want to get this into Nightly for testing early, or else we should just skip Release and do a fast-follow. |
* Extract controller into it's own class. Implement find dupes and filter based on username. Create edit login controller. Add text watchers and check for duplicates. Edit controller test * Find duplicates and save to store * Retrieve duplicates from AC and check list on username text changed Move duplicates logic into the controller * Add glean pings for delete and edit. Move logic for login manipulation into the datastore. * Use correct threads in controller. Enable save button when applicable. Save enabled in datastore. Move login data to datastore Rebase with password error states Update metrics to be more specific for edit * Create logins controller for AC calls * Interactor and controller methods for edit login. Add edit view to separate out some layout manipulation. Inflate view in edit fragment. Double layout showing up. Edit view Controller tests Controller tests passing Interactor tests Lint and detekt cleanup * Remove datastore and use storage controller for all logins calls to password storage. Addressed comments Lint : Rebase - 1
For QAThere are still a few bugs with this depending on the next nightly build of AC (#12651) |
This is not fixed yet.
|
That is a bug with Save and Autofilling credentials. I will file that as a separate ticket. This issue is only applicable for editing a saved login. |
Hi @eliserichards, I've tested again on Beta 80.0.0-beta.1, and on the 7/30 Nightly build with Samsung Galaxy Tab S6 (Android 9), with twitter.com account. Using the following STR:
Actual results: |
Thanks @softvision-miralobontiu - we pulled those STR into #12751 |
Acceptance Criteria
getPotentialDupesIgnoringUsername(login)
inSyncableLoginsStorage
┆Issue is synchronized with this Jira Task
The text was updated successfully, but these errors were encountered: