8000 PM-13066 - Add FAB on various screens by phil-livefront · Pull Request #1028 · bitwarden/ios · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

PM-13066 - Add FAB on various screens #1028

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

Merged
merged 17 commits into from
Oct 16, 2024
Merged

Conversation

phil-livefront
Copy link
Collaborator
@phil-livefront phil-livefront commented Oct 9, 2024

🎟️ Tracking

PM-13066

📔 Objective

  • Implemented a floating action button to the bottom right of the VaultListView, VaultGroupView, VaultAutofillListView, SendListView, VaultItemSelectionView, and FoldersView.
  • Created a CircleButtonStyle and a FloatingActionButton.
  • Added extensions on View to create an add and edit floating action buttons which were used in the views above to prevent duplication.
  • Confirmed with design that the FAB should be shown during the loading and empty state. I did however follow the pattern to hide the FAB when searching.
  • I didn't remove the "+" from the nav bar because that will be done in this ticket and i wanted to keep these changes minimal.
  • The current plus.pdf is actually a little off centered. I am going to be replacing it in the icons update ticket so I left it alone in this PR but you may notice the "+" looks a bit weird on the FAB and thats why.
  • Sorry about the large file change amount, its mostly snapshots though.

** Going to confirm with design about the empty states... After seeing some snapshots with large font, it just doesn't make sense to have two buttons overlapping that do the same thing. Keeping as is for now since figma matches but might update in this Pr or a future one.

Update from design: Currently working on a design update and approved keeping the FAB on the empty state as-is until coming to a decision.

📸 Screenshots

see snapshots for all of the screenshot changes but heres an example.

Simulator Screenshot - iPhone 15 Pro - 2024-10-09 at 13 20 22

⏰ 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
codecov bot commented Oct 9, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 89.25%. Comparing base (cb856d1) to head (6475003).
Report is 1 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #1028      +/-   ##
==========================================
+ Coverage   89.22%   89.25%   +0.03%     
==========================================
  Files         665      667       +2     
  Lines       41788    41924     +136     
==========================================
+ Hits        37285    37421     +136     
  Misses       4503     4503              

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

Copy link
Contributor
github-actions bot commented Oct 9, 2024

Logo
Checkmarx One – Scan Summary & Details8ff53318-6a1e-4e18-b19f-9e8963f33aaf

No New Or Fixed Issues Found

8000

Copy link
Collaborator
@matt-livefront matt-livefront left a comment

Choose a reason for hiding this comment

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

If there's a bunch of items in the vault list, it seems like this overlaps the last item. Should we add additional padding to the bottom of the list to account for the FAB?

Simulator.Screen.Recording.-.iPhone.15.Pro.-.2024-10-09.at.13.34.45.mp4

The FAB looks like it's used in a few different places. Do you know if there are other tickets for that, or should we do that as part of this? I think this includes VaultGroupView, VaultAutofillListView, SendListView, VaultItemSelectionView, and FoldersView (anywhere addToolbarItem is used).

Copy link
Contributor
@KatherineInCode KatherineInCode left a comment

Choose a reason for hiding this comment

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

🤔 There are a couple of these screenshots that have the FAB that I'm wondering if they should, such as loading, or the empty state where there's an "Add Item" button front and center. Is this what we want, or will more conditional logic for this be in a future PR?

@@ -68,6 +68,14 @@ class VaultListViewTests: BitwardenTestCase {
XCTAssertEqual(processor.dispatchedActions.last, .addItemPressed)
}

/// Tapping the new login floating acrtion button dispatches the `.addItemPressed` action.`
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
/// Tapping the new login floating acrtion button dispatches the `.addItemPressed` action.`
/// Tapping the new login floating action button dispatches the `.addItemPressed` action.`

@phil-livefront
Copy link
Collaborator Author

🤔 There are a couple of these screenshots that have the FAB that I'm wondering if they should, such as loading, or the empty state where there's an "Add Item" button front and center. Is this what we want, or will more conditional logic for this be in a future PR?

Im about to make a commit to fix a lot of what Matt brought up and add the FAB to the other screens as well. I did confirm with design that the FAB should be on the loading screen and on the figma designs they show the FAB being on the empty state as well.

@phil-livefront phil-livefront marked this pull request as draft October 10, 2024 21:52
@phil-livefront phil-livefront changed the title PM-13066 - Add vault floating action button PM-13066 - Add FAB on various screens Oct 11, 2024
@phil-livefront phil-livefront marked this pull request as ready for review October 11, 2024 05:39
@phil-livefront phil-livefront marked this pull request as draft October 11, 2024 20:36
@phil-livefront phil-livefront marked this pull request as ready for review October 15, 2024 19:15
Copy link
Collaborator
@matt-livefront matt-livefront left a comment

Choose a reason for hiding this comment

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

Just a few additional comments, but otherwise this looks great. There's a few lint warnings that should get resolved too.

@phil-livefront phil-livefront merged commit 20da6cf into main Oct 16, 2024
9 checks passed
@phil-livefront phil-livefront deleted the phil/PM-13066-add-vault-fab branch October 16, 2024 14:46
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.

3 participants
0