bitwarden / clients

Bitwarden client apps (web, browser extension, desktop, and cli).
https://bitwarden.com
Other
9.06k stars 1.2k forks source link

[PM-9318] Fix username on protonpass import #9889

Closed djsmith85 closed 2 months ago

djsmith85 commented 3 months ago

🎟ī¸ Tracking

https://bitwarden.atlassian.net/browse/PM-9318

📔 Objective

Protonpass has changed their export format and this broke the import of usernames

Renamed username to itemEmail and added itemUsername

⏰ Reminders before review

đŸĻŽ Reviewer guidelines

codecov[bot] commented 3 months ago

Codecov Report

All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 29.52%. Comparing base (8f66d60) to head (315e511). Report is 1 commits behind head on main.

Additional details and impacted files ```diff @@ Coverage Diff @@ ## main #9889 +/- ## ========================================== - Coverage 29.53% 29.52% -0.01% ========================================== Files 2538 2538 Lines 74159 74160 +1 Branches 13855 13855 ========================================== - Hits 21905 21899 -6 - Misses 50594 50601 +7 Partials 1660 1660 ```

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

quexten commented 3 months ago

:question: question: In the future, if Proton does split it up by username and email (auto-detecting this by the field), would it make sense to detect which field is set on the Proton export, and set the bitwarden username to the export itemUsername/itemEmail if just one of the proton export fields is set, and if both are set do bitwarden-username = proton.itemUsername, bitwarden-custom-field-email=proton.itemEmail? (Most of my bitwarden accounts have their email set in the username and it feels be unintuitive to have no username but only a custom email field)

github-actions[bot] commented 3 months ago

Logo Checkmarx One – Scan Summary & Details – 87e89dca-e193-4114-9955-77306ccc3e1e

No New Or Fixed Issues Found