feat: addition of a button below existing one for the routing to the …#455
Conversation
…cross-unit dashboard
cillynder
left a comment
There was a problem hiding this comment.
The dashboard button should be above the history button as it would generally be more important.
| color="primary" | ||
| mat-fab | ||
| extended | ||
| aria-label="view all projects" |
There was a problem hiding this comment.
| aria-label="view all projects" | |
| aria-label="view previous projects" |
| extended | ||
| aria-label="view all projects" | ||
| > | ||
| <mat-icon style="color: white">history</mat-icon> View all |
There was a problem hiding this comment.
| <mat-icon style="color: white">history</mat-icon> View all | |
| <mat-icon style="color: white">history</mat-icon> View previous |
Should be changed so it's distinct from the other button.
|
@BrianDangDev |
|
Hi @owens-hub-git, I reviewed and tested the branch locally. It works well, but at the moment both buttons seem to go to the same page. |
|
@WaelAlahamdi, This was mentioned in the description about what should happen when clicking the button as we are still working on the page to route to |
WaelAlahamdi
left a comment
There was a problem hiding this comment.
Thanks @owens-hub-git for clarifying. I reviewed and tested this locally, and it works as expected for the current scoped UI change. Approved based on the PR description.
|
Approved and Merged |
Description
Strict frontend change in the home component where I added a button underneath the current view all for previous units. This still routes to the same component for previous units, but will be the start for the cross-unit dashboard development
Type of change
How Has This Been Tested?
Testing Checklist:
Checklist: