-
Notifications
You must be signed in to change notification settings - Fork 858
[PM-20508] Centralize passkey credential entry creation #5033
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
base: main
Are you sure you want to change the base?
Conversation
New Issues (2)Checkmarx found the following issues in this Pull Request
Fixed Issues (8)Great job! The following issues were fixed in this Pull Request
|
6832607
to
3fa91cc
Compare
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #5033 +/- ##
==========================================
- Coverage 83.85% 83.57% -0.28%
==========================================
Files 596 620 +24
Lines 48855 49479 +624
Branches 6711 6747 +36
==========================================
+ Hits 40966 41354 +388
- Misses 5618 5840 +222
- Partials 2271 2285 +14 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
68f8116
to
e4e9836
Compare
app/src/test/java/com/x8bit/bitwarden/data/vault/datasource/sdk/model/CipherViewUtil.kt
Dismissed
Show dismissed
Hide dismissed
app/src/test/java/com/x8bit/bitwarden/data/vault/datasource/sdk/model/CipherViewUtil.kt
Dismissed
Show dismissed
Hide dismissed
e4e9836
to
54dd5ca
Compare
54dd5ca
to
a76dec6
Compare
Move the responsibility of building credential entries from `Fido2ProviderProcessor` to `Fido2CredentialManager`. This change centralizes the credential handling and simplifies the code in `Fido2ProviderProcessor` by delegating this task. Key changes: - **Fido2CredentialManager:** - Implemented `getCredentialEntries()` to handle the retrieval and creation of `CredentialEntry` objects. - Now uses the `VaultRepository` to fetch and decrypt credential data. - Uses `EnvironmentRepository` to get base icon url. - Now uses Glide for network image loading (currently disabled). - Includes logic to handle biometric prompts. - **Fido2ProviderProcessor:** - Removed the logic for building `CredentialEntry`. - Now relies on `Fido2CredentialManager` to provide the credential entries. - Updated logic in `handleFido2GetCredentialsRequest` to delegate credential retrieval to manager. - **Fido2CompletionManager:** - Updated to use `CredentialEntry`. - Updated logic to use new `GetFido2CredentialsResult`. - **VaultItemListingViewModel:** - Updated logic in `handleFido2GetCredentialsRequest` to delegate credential retrieval to manager. - **Tests:** - Updated unit tests to reflect the changes in `Fido2ProviderProcessor`, `VaultItemListingScreenTest`, and `Fido2CompletionManager`. - **Dependencies:** - Removed redundant dependencies. - **Cleanup:** - Removed unnecessary code and comments. - **Module dependency:** - Added dispatcher and environment modules dependencies to Fido2Provider module. - **LocalManagerProvider:** - `Fido2CompletionManager` doesn't need `IntentManager` anymore.
a76dec6
to
09c1c95
Compare
🎟️ Tracking
Resolves PM-20176
Resolves PM-20127
📔 Objective
Move the responsibility of building credential entries from
Fido2ProviderProcessor
toFido2CredentialManager
. This change centralizes the credential handling and simplifies the code inFido2ProviderProcessor
by delegating this task.Key changes:
getCredentialEntries()
to handle the retrieval and creation ofCredentialEntry
objects.VaultRepository
to fetch and decrypt credential data.EnvironmentRepository
to get base icon url.CredentialEntry
.Fido2CredentialManager
to provide the credential entries.handleFido2GetCredentialsRequest
to delegate credential retrieval to manager.CredentialEntry
.GetFido2CredentialsResult
.handleFido2GetCredentialsRequest
to delegate credential retrieval to manager.Fido2ProviderProcessor
,VaultItemListingScreenTest
, andFido2CompletionManager
.Fido2CompletionManager
doesn't needIntentManager
anymore.⏰ Reminders before review
🦮 Reviewer guidelines
:+1:
) or similar for great changes:memo:
) or ℹ️ (:information_source:
) for notes or general info:question:
) for questions:thinking:
) or 💭 (:thought_balloon:
) for more open inquiry that's not quite a confirmed issue and could potentially benefit from discussion:art:
) for suggestions / improvements:x:
) or:warning:
) for more significant problems or concerns needing attention:seedling:
) or ♻️ (:recycle:
) for future improvements or indications of technical debt:pick:
) for minor or nitpick changes