[PM-34106] chore: Consolidate KeychainItem into BitwardenKit via protocol#2492
[PM-34106] chore: Consolidate KeychainItem into BitwardenKit via protocol#2492KatherineInCode merged 14 commits intomainfrom
Conversation
|
Great job! No new security vulnerabilities introduced in this pull request |
|
Overall Assessment: APPROVE Reviewed the consolidation of Code Review DetailsNo findings. |
Codecov Report❌ Patch coverage is Additional details and impacted files@@ Coverage Diff @@
## main #2492 +/- ##
==========================================
- Coverage 86.91% 85.80% -1.11%
==========================================
Files 1846 2076 +230
Lines 163345 178294 +14949
==========================================
+ Hits 141971 152989 +11018
- Misses 21374 25305 +3931 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|

🎟️ Tracking
https://bitwarden.atlassian.net/browse/PM-34106
📔 Objective
This expands what was the
KeychainStorageKeyPossessingprotocol to include other properties fromKeychainItem, and then renames it toKeychainItemwhile also renaming the formerKeychainItemclasses toBitwardenKeychainItemandAuthenticatorKeychainItem. This will make it easier to do further refactoring of our keychain code by making it easier to consolidate more things intoBitwardenKit.I considered turning this into a struct with extensions with static members, like
FeatureFlag, but because manyKeychainItemenum cases take an associated value (usually of the user ID), those would have to become static functions instead of static variables, and I wasn't particularly fond of that. However, I do think if we're good with the static functions, we could take that route instead, though I feel like it's six of one and half dozen of another.