-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
[PM-7611] Create a new vault settings component [UI changes] #9220
[PM-7611] Create a new vault settings component [UI changes] #9220
Conversation
- Copy existing vault-settings component - Make new component standalone - Replace app-header with popup-header - Replace nav-buttons with bit-item - Register route to show new component when extension refresh flag is enabled
…s/pm-7611/create-a-new-vault-settings-component-UI-changes
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #9220 +/- ##
==========================================
- Coverage 28.14% 28.13% -0.02%
==========================================
Files 2361 2362 +1
Lines 69846 69880 +34
Branches 13133 13139 +6
==========================================
Hits 19660 19660
- Misses 48629 48663 +34
Partials 1557 1557 ☔ View full report in Codecov by Sentry. |
New Issues
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good! Just a few minor suggestions.
apps/browser/src/vault/popup/settings/vault-settings-v2.component.ts
Outdated
Show resolved
Hide resolved
…s/pm-7611/create-a-new-vault-settings-component-UI-changes
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you!
…s/pm-7611/create-a-new-vault-settings-component-UI-changes
…s/pm-7611/create-a-new-vault-settings-component-UI-changes
* Create vault-settings-v2 component - Copy existing vault-settings component - Make new component standalone - Replace app-header with popup-header - Replace nav-buttons with bit-item - Register route to show new component when extension refresh flag is enabled * Move sync functionality to vault-settings-v2 * Use anchors instead of buttons when navigating to a sub-page * Removed unneeded component within routing * Use new ToastService instead of PlatformUtils * Remove unused MessagingService --------- Co-authored-by: Daniel James Smith <djsmith85@users.noreply.github.com>
Type of change
Objective
With #8840 the navigational changes were made. This is meant to update UI for the extensions refresh according to the new design.
The currently missing trash anchor and page will be added with PM-8125
Code changes
sync.component
will need to be deleted when we fully switch over to the new designScreenshots
Before
After
Before you submit