-
Notifications
You must be signed in to change notification settings - Fork 30
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
Change vertical gap to 4px in beta containers #13126
Merged
Merged
+66
−34
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Size Change: +58 B (+0.01%) Total Size: 884 kB ℹ️ View Unchanged
|
abeddow91
reviewed
Jan 13, 2025
Fweddi
force-pushed
the
fp/meta-spacing
branch
2 times, most recently
from
January 14, 2025 11:34
d7acc43
to
2986579
Compare
Fweddi
force-pushed
the
fp/meta-spacing
branch
from
January 16, 2025 10:46
2986579
to
c0ec4c5
Compare
github-actions
bot
removed
the
run_chromatic
Runs chromatic when label is applied
label
Jan 16, 2025
Fweddi
force-pushed
the
fp/meta-spacing
branch
2 times, most recently
from
January 16, 2025 16:06
b381d69
to
1e17403
Compare
Fweddi
force-pushed
the
fp/meta-spacing
branch
from
January 16, 2025 16:07
1e17403
to
8a74765
Compare
Fweddi
changed the title
Change gap to 4px in beta containers
Change vertical gap to 4px in beta containers
Jan 16, 2025
Hello 👋! When you're ready to run Chromatic, please apply the You will need to reapply the label each time you want to run Chromatic. |
github-actions
bot
removed
the
run_chromatic
Runs chromatic when label is applied
label
Jan 16, 2025
Fweddi
force-pushed
the
fp/meta-spacing
branch
from
January 16, 2025 16:23
8a74765
to
90ee12c
Compare
github-actions
bot
removed
the
run_chromatic
Runs chromatic when label is applied
label
Jan 16, 2025
github-actions
bot
removed
the
run_chromatic
Runs chromatic when label is applied
label
Jan 21, 2025
abeddow91
approved these changes
Jan 21, 2025
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.
Nice solution ✨ One comment but its non blocking.
github-actions
bot
removed
the
run_chromatic
Runs chromatic when label is applied
label
Jan 21, 2025
Fweddi
force-pushed
the
fp/meta-spacing
branch
from
January 22, 2025 09:34
0ff68fc
to
d8d6312
Compare
Fweddi
force-pushed
the
fp/meta-spacing
branch
from
January 22, 2025 09:57
d8d6312
to
a60723d
Compare
github-actions
bot
removed
the
run_chromatic
Runs chromatic when label is applied
label
Jan 22, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this change?
For cards belonging to a beta container, we want to reduce the vertical gap between the image and the meta (i.e. comment count) to tiny (4px).
To achieve this, I have separated out row gaps (vertical) from column gaps (horizontal). These should be the same except for the new desired condition.
The new condition is low down in the priority order. This means there will be some exceptions to this condition, e.g. a 'scrollable small' container is a beta container, but prefers a medium size gap.
I am unsure if this priority order is correct - would be good to have another pair of eyes.
Why?
Design spec.
Screenshots