-
Notifications
You must be signed in to change notification settings - Fork 429
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
fix: Manage members layout is broken #3058
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Uffizzi Preview |
@@ -26,7 +26,7 @@ import PageTitle from 'components/PageTitle' | |||
import { getStore } from 'common/store' | |||
import { getRoles } from 'common/services/useRole' | |||
|
|||
const widths = [450, 150, 100] | |||
const widths = [450, 150, 100, 250, 235, 255] |
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.
I'd quite like to understand why we define these widths here rather than just directly in the style objects below.
It also would make sense to my somewhat picky brain if these were ordered, either smallest to largest or largest to smallest, I'm not that fussy!
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.
It seems that initially this array was used to give sizes to the panelSearch component, as I worked on that component I added those values to the array.
Re-ordered.
I have tested this via the preview and it looks good to me, but I've added a comment on the implementation. |
Thanks for submitting a PR! Please check the boxes below:
pre-commit
to check lintingChanges
Before:

Now:

How did you test this code?