Closed djsmith85 closed 2 months ago
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.
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
: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)
Checkmarx One â Scan Summary & Details â 87e89dca-e193-4114-9955-77306ccc3e1e
đī¸ Tracking
https://bitwarden.atlassian.net/browse/PM-9318
đ Objective
Protonpass has changed their export format and this broke the import of usernames
Renamed
username
toitemEmail
and addeditemUsername
â° 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