-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Chip right height according to view #7976
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.
PR Summary
This pull request introduces size adjustments for the AvatarChip component to improve visual consistency across different view types, particularly for Kanban and list views.
- Added
size
prop toAvatarChip
inpackages/twenty-ui/src/display/chip/components/AvatarChip.tsx
- Modified
RecordIndexRecordChip
inpackages/twenty-front/src/modules/object-record/record-index/components/RecordIndexRecordChip.tsx
to setChipSize.Large
for Kanban view - Updated
Chip
component inpackages/twenty-ui/src/display/chip/components/Chip.tsx
to adjust height based onsize
prop - Simplified
OverflowingTextWithTooltip
usage inChip
component by directly passing thesize
prop
3 file(s) reviewed, 1 comment(s)
Edit PR Review Bot Settings | Greptile
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.
LGTM thank you!
@@ -17,6 +20,7 @@ export const RecordIdentifierChip = ({ | |||
variant, | |||
}: RecordIdentifierChipProps) => { | |||
const { onIndexIdentifierClick } = useContext(RecordIndexRootPropsContext); | |||
const recordIndexViewType = useRecoilValue(recordIndexViewTypeState); |
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 feels like it would be cleaner to pass introduce size in this component and pass the chip size from the level right above, similar what we probably do with variant
no? Can't tell exactly why but it feels a bit odd here
No description provided.