-
Notifications
You must be signed in to change notification settings - Fork 0
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
feat: #569 implement the redesign for dashboard and side nav #613
base: main
Are you sure you want to change the base?
feat: #569 implement the redesign for dashboard and side nav #613
Conversation
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.
One suggestion I would give is to start replacing the imports to use the path definition set on the tsconfig and vite config files to avoid path navigations and possibly issues when importing or copying imports from other files.
frontend/src/App.tsx
Outdated
@@ -46,6 +48,33 @@ const protectedRoutes: RouteObject[] = [ | |||
} | |||
]; | |||
|
|||
// Tanstack Query Config |
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.
Can we move this into a separate file?
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.
done
min-width: 1rem; | ||
min-height: 1rem; | ||
} | ||
.divisory { |
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.
As the hr tag was removed from the template file, I think is safe to remove this css class from here as it is not being required anymore
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.
no there's still an hr element at line 48 😛
|
||
.chart-holder { | ||
|
||
.cds--cc--axes g.axis g.tick text { |
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.
Shouldn't we use the vars.$bcgov-prefix
variable?
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.
the vars.$bcgov-prefix is 'bx', i think the prefix here is special for the chart component, honestly i didn't find this css having any effects, but left it here from the previous code
{ | ||
!recentOpeningsQuery.isLoading && recentOpeningsQuery.data?.data.length ? | ||
( | ||
<Table |
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.
One suggestion here would be to try to generify this table, something like this I am doing on another PR.
With a few changes on the headers object, we can even set if a specific field should use a component to render (such as the date, status, truncated texts). This would reduce code duplication, as we can just provide to the data table the page content, pagination content and possible empty scenario flags/texts
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.
yeah that's a good idea, it might be better to do it in a separate issue, then we can have all tables to use the generic table with loading and error handling
Description
Implements #569
Implemented the new design for dashboard and and side nav
Type of change
Please delete options that are not relevant.
ick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc... -->
Thanks for the PR!
Deployments, as required, will be available below:
Please create PRs in draft mode. Mark as ready to enable:
After merge, new images are deployed in:
Thanks for the PR!
Deployments, as required, will be available below:
Please create PRs in draft mode. Mark as ready to enable:
After merge, new images are deployed in: