-
Notifications
You must be signed in to change notification settings - Fork 221
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(clerk-js): Align some sections in User Profile with the designs #2814
fix(clerk-js): Align some sections in User Profile with the designs #2814
Conversation
🦋 Changeset detectedLatest commit: cf24ec6 The changes in this PR will be included in the next version bump. This PR includes changesets to release 0 packagesWhen changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
id='connectedAccounts' | ||
sx={t => ({ | ||
borderRadius: t.radii.$lg, | ||
':hover': { backgroundColor: t.colors.$neutralAlpha50 }, |
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 avoid the duplication here by putting the styles inside ProfileSection.Item
?
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.
We can't move them in ProfileSection.Item
as we use it for stuff that don't need the hover state and the border radius but we can create a new component or add a prop to add those styles.
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.
We can move them in and add a prop or make a small wrapper as you said. I prefer the wrapper tbh.
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 only thing I don't like about the wrapper is that it's can be a bit confusing as it would be the same thing, the hover state is like having a variant.
@@ -62,6 +62,7 @@ export const ArrowBlockButton = React.forwardRef<HTMLButtonElement, ArrowBlockBu | |||
justifyContent: 'center', | |||
borderColor: theme.colors.$neutralAlpha100, | |||
alignItems: 'center', | |||
padding: `${theme.space.$1x5} ${theme.space.$3} ${theme.space.$1x5} ${theme.space.$2x5}`, |
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.
Why is this necessary? Isn't it going to make most screens deviate from designs now?
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.
This is the padding that the designs have.
@@ -128,7 +128,7 @@ const ProfileSectionItem = (props: ProfileSectionItemProps) => { | |||
justifyContent: 'space-between', | |||
width: '100%', | |||
alignItems: 'center', | |||
padding: `${t.space.$1x5} ${t.space.$none} ${t.space.$1x5} ${t.space.$4}`, | |||
padding: `${t.space.$1x5} ${t.space.$3} ${t.space.$1x5} ${t.space.$2x5}`, |
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.
Ditto
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.
This change is made to be completely aligned with the designs
!preview |
Hey @anagstef, your preview is available.
|
ba41574
to
770c57b
Compare
770c57b
to
1647a19
Compare
!preview |
!preview |
!preview |
Description
This PR adds a hover state for all profile section items that include an action menu (eg. Emails, Phone numbers etc.)
Before
After
Checklist
npm test
runs as expected.npm run build
runs as expected.Type of change