Skip to content

Allow theme to specify Anchor gap #6114

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

Merged
merged 2 commits into from
May 5, 2022
Merged

Allow theme to specify Anchor gap #6114

merged 2 commits into from
May 5, 2022

Conversation

taysea
Copy link
Collaborator

@taysea taysea commented May 5, 2022

What does this PR do?

Adds theme.anchor.gap to allow the gap to be specified by the theme. Necessary for HPE theme.

Where should the reviewer start?

base.js

What testing has been done on this PR?

Tested in story and added jest test.

How should this be manually tested?

Do Jest tests follow these best practices?

  • screen is used for querying.
  • The correct query is used. (Refer to this list of queries)
  • userEvent is used in place of fireEvent.
  • asFragment() is used for snapshot testing.

Any background context you want to provide?

What are the relevant issues?

Screenshots (if appropriate)

Do the grommet docs need to be updated?

Yes.

Should this PR be mentioned in the release notes?

Yes.

Is this change backwards compatible or is it a breaking change?

Backwards compatible.

@taysea taysea requested review from halocline and britt6612 May 5, 2022 21:43
Copy link
Collaborator

@britt6612 britt6612 left a comment

Choose a reason for hiding this comment

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

Lets just add to grommet docs before we forget

@taysea taysea removed the request for review from halocline May 5, 2022 23:16
@ericsoderberghp ericsoderberghp merged commit 316e802 into grommet:master May 5, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants