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

feat!: Remove gap from Card #1785

Open
wants to merge 3 commits into
base: develop
Choose a base branch
from

Conversation

RubenSibon
Copy link
Contributor

@RubenSibon RubenSibon commented Dec 11, 2024

Describe the pull request

Remove the gap token and CSS property from Card. Users can now use the spacing CSS classes or components (i.e. Column) to control spacing inside cards.

What

  • Removes the gap token;
  • Removes the gap property from .ams-card;
  • Adds bottom margins to Card's in stories.

Why

We do not want to enforce lay-out or spacing of children of Card. Card should just be a wrapper with a link.

Checklist

Before submitting your pull request, please ensure you have done the following. Check each checkmark if you have done so or if it wasn't necessary:

  • Add or update unit tests
  • Add or update documentation
  • Add or update stories
  • Add or update exports in index.* files
  • Start the PR title with a Conventional Commit prefix, as explained here.

Additional notes

@@ -36,7 +36,7 @@ type Story = StoryObj<typeof meta>
export const Default: Story = {
args: {
children: [
<Heading size="level-4" key={1}>
<Heading key={1} className="ams-mb--sm" size="level-4">
Copy link
Contributor

Choose a reason for hiding this comment

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

Should be xs, I think. The CSS utils use the grid space, which is bigger than the regular space. The spacing system is still a little confusing, I think

Copy link
Contributor

Choose a reason for hiding this comment

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

I was going to reply, “No, they don’t; margin utils use component space, duh”, but then… they appeared to use grid space 😳. That has never been my intention; I have no idea how that got merged.

Bas, Inge and I discussed the approach for designing white space between text components this morning. Bas may have some early conclusions at the end of this week or early January. This PR is pretty isolated, so most of its work will survive; let’s revisit it by then.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Good that we find this out now before the 1.0.

The spacing system seems to be a little confusing indeed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

3 participants