Skip to content
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

Merged
merged 4 commits into from
Oct 23, 2024
Merged

Conversation

ehconitin
Copy link
Contributor

No description provided.

Copy link
Contributor

@greptile-apps greptile-apps bot left a 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 to AvatarChip in packages/twenty-ui/src/display/chip/components/AvatarChip.tsx
  • Modified RecordIndexRecordChip in packages/twenty-front/src/modules/object-record/record-index/components/RecordIndexRecordChip.tsx to set ChipSize.Large for Kanban view
  • Updated Chip component in packages/twenty-ui/src/display/chip/components/Chip.tsx to adjust height based on size prop
  • Simplified OverflowingTextWithTooltip usage in Chip component by directly passing the size prop

3 file(s) reviewed, 1 comment(s)
Edit PR Review Bot Settings | Greptile

Copy link
Contributor

@martmull martmull left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM thank you!

@martmull martmull enabled auto-merge (squash) October 23, 2024 07:38
@martmull martmull enabled auto-merge (squash) October 23, 2024 07:38
@@ -17,6 +20,7 @@ export const RecordIdentifierChip = ({
variant,
}: RecordIdentifierChipProps) => {
const { onIndexIdentifierClick } = useContext(RecordIndexRootPropsContext);
const recordIndexViewType = useRecoilValue(recordIndexViewTypeState);
Copy link
Member

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

@martmull martmull merged commit a35d888 into twentyhq:main Oct 23, 2024
16 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants