-
Notifications
You must be signed in to change notification settings - Fork 15
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 Table paddings for last column #4677
Conversation
🦋 Changeset detectedLatest commit: dda0975 The changes in this PR will be included in the next version bump. This PR includes changesets to release 2 packages
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 |
@toptal-bot run package:alpha-release |
Your alpha package is ready 🎉 |
@toptal-anvil ping reviewers |
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 miss the storybook link, but the happo diffs are looking good 👍🏻
Co-authored-by: Diogo Lessa <diogo.lessa@toptal.com>
@diogolessa the temploy is http://picasso.toptal.net/bill-fix-table-paddings |
@toptal-anvil ping reviewers |
Description
By some reason now we have the last cell having custom extra padding. After discussion with Milos and checking Figma - https://www.figma.com/design/q2nvjiyO2CLqBv4DeJnU3i/Product-Library-Documentation?node-id=476-9897&t=ywR92i2wXfDtSkiq-4. We agreed that there should be no extra padding and the left padding for the first cell/column should be the same as the right padding for the last column.
How to test
Check padding for Table component in storybook.
Development checks
picasso-tailwind-merge
requires major update (check itsREADME.md
)props
in component with documentationexamples
for componentBreaking change
PR commands
List of available commands:
@toptal-bot run package:alpha-release
- Release alpha version@toptal-anvil ping reviewers
- Ping for reviewsPR Review Guidelines
When to approve? ✅
You are OK with merging this PR and
nit:
to your comment. (ex.nit: I'd rename this variable from makeCircle to getCircle
)When to request changes? ❌
You are not OK with merging this PR because
When to comment (neither ✅ nor ❌)
You want your comments to be addressed before merging this PR in cases like:
How to handle the comments?