-
Notifications
You must be signed in to change notification settings - Fork 1k
add support for border between in border array #6642
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
add support for border between in border array #6642
Conversation
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 work so far! It looks like there may be a few other places in Box.js
where we may want to check if border is an array and it container side='between'. See line 103 of Box.js where it has if ( (border === 'between' || (border && border.side === 'between')) && !gap )
. Also see line 221 where we have gap={ (boxOptions?.cssGap || cssGap) && gap && gap !== 'none' && border !== 'between' && border?.side !== 'between' && gap }
@jcfilben Do you think that the refinement requests you listed should block this current PR? or can we file a separate issue to track it? |
It looks like the changes requested already made their way into the PR. So no need to file a separate issue for this. |
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.
Looks good!
What does this PR do?
Add support for using between border in border array props
Where should the reviewer start?
Box.js
What testing has been done on this PR?
yarn test
passedHow should this be manually tested?
A storybook example added
Do Jest tests follow these best practices?
screen
is used for querying.userEvent
is used in place offireEvent
.asFragment()
is used for snapshot testing.Any background context you want to provide?
What are the relevant issues?
#6640
Screenshots (if appropriate)
Do the grommet docs need to be updated?
No
Should this PR be mentioned in the release notes?
Is this change backwards compatible or is it a breaking change?
Compatible