8000 [PM-15634] Add intermediate Export settings view by fedemkr · Pull Request #1227 · bitwarden/ios · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

[PM-15634] Add intermediate Export settings view #1227

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

Closed
wants to merge 15 commits into from

Conversation

fedemkr
Copy link
Member
@fedemkr fedemkr commented Dec 23, 2024

🎟️ Tracking

PM-15634

📔 Objective

Add intermediate Export settings view so that the user can choose whether to export to a file or using the Credential Exchange flow.

⚠️ Depends on #1223, so it should be merged after it.

Notes

The old "Export vault" view files were moved to another folder, so now we have this structure:

  • ExportVault
    • Export
      • ExportSettingsView
    • ExportVaultCXF
      • TODO in next PR
    • ExportVaultToFile
      • ExportVaultView

📸 Screenshots

Export.intermediate.view.mov

⏰ Reminders before review

  • Contributor guidelines followed
  • All formatters and local linters executed and passed
  • Written new unit and / or integration tests where applicable
  • Protected functional changes with optionality (feature flags)
  • Used internationalization (i18n) for all UI strings
  • CI builds passed
  • Communicated to DevOps any deployment requirements
  • Updated any necessary documentation (Confluence, contributing docs) or informed the documentation team

🦮 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

Copy link
Contributor
github-actions bot commented Dec 23, 2024

Logo
Checkmarx One – Scan Summary & Details948adde2-8232-4138-acee-f3f60f4a423b

No New Or Fixed Issues Found

Copy link
codecov bot commented Dec 23, 2024

Codecov Report

Attention: Patch coverage is 93.49776% with 29 lines in your changes missing coverage. Please review.

Project coverage is 89.60%. Comparing base (43e1883) to head (00f2d35).
Report is 12 commits behind head on main.

Files with missing lines Patch % Lines
...denShared/UI/Tools/ImportCXP/ImportCXPModule.swift 0.00% 6 Missing ⚠️
...nShared/UI/Platform/Application/AppProcessor.swift 66.66% 5 Missing ⚠️
...Tools/ImportCXP/ImportCXP/ImportCXPProcessor.swift 87.80% 5 Missing ⚠️
...twardenShared/Core/Platform/Utilities/AnyKey.swift 50.00% 4 Missing ⚠️
...e/Tools/Repositories/ImportCiphersRepository.swift 66.66% 3 Missing ⚠️
...ore/Tools/Utilities/CredentialManagerFactory.swift 50.00% 3 Missing ⚠️
...d/UI/Tools/ImportCXP/ImportCXP/ImportCXPView.swift 97.43% 2 Missing ⚠️
...nShared/Core/Platform/Services/ClientService.swift 66.66% 1 Missing ⚠️
Additional details and impacted files
@@            Coverage Diff             @@
##             main    #1227      +/-   ##
==========================================
+ Coverage   89.47%   89.60%   +0.12%     
==========================================
  Files         700      711      +11     
  Lines       44733    45137     +404     
==========================================
+ Hits        40026    40445     +419     
+ Misses       4707     4692      -15     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🎨 What do you think about renaming the containing folder from Export to ExportSettings since these files are all using the ExportSettings prefix?

Comment on lines +17 to +31
SettingsListItem(Localizations.exportVaultToAFile) {
store.send(.exportToFileTapped)
} trailingContent: {
chevron
}
.accessibilityIdentifier("ExportVaultToAFileLabel")
.cornerRadius(10)

SettingsListItem(Localizations.exportVaultToAnotherApp) {
store.send(.exportToAppTapped)
} trailingContent: {
chevron
}
.accessibilityIdentifier("ExportVaultToAnotherAppLabel")
.cornerRadius(10)
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will b 8000 e displayed to describe this comment to others. Learn more.

⛏️ It looks like both of these items are displaying the bottom divider. Should that be removed? Alternatively, should both of these options be grouped together, similar to the main settings view?

Screenshot 2025-01-03 at 3 44 57 PM

Simulator Screenshot - iPhone 16 Pro - 2025-01-03 at 15 45 02

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice catch the divider, I'll fix that! As to group them, in Figma they appear separated so I based the UI on that.

Comment on lines +37 to 38
/// A route to the export vault settings view.
case exportVault
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⛏️ Slight preference to renaming this to exportSettings to match the prefix for the files associated with this route.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'll clarify the comment, as this route could go to the export settings view as well as to the export to file view depending on whether the CXP Export feature flag is enabled. That's why I left it as exportVault as it has a more generic interpretation.

Base automatically changed from PM-14800/impl-cxp-import-flow to main January 6, 2025 12:35
@fedemkr
Copy link
Member Author
fedemkr commented Jan 8, 2025

Closing this to be replaced by a new PR #1245 to ease merging from main and have a clearer history. cc: @matt-livefront feedback on this PR has been addressed in the new one.

@fedemkr fedemkr closed this Jan 8, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants
0