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(Menu): match css structure #8820
Conversation
Preview: https://patternfly-react-pr-8820.surge.sh A11y report: https://patternfly-react-pr-8820-a11y.surge.sh |
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.
CSS-wise looks good. Had some React comments below. Additionally just needs a codemod issue opened for any applicable changes being made.
<MenuSearch> | ||
<MenuSearchInput>Unselectable text displayed at the top of the menu</MenuSearchInput> | ||
</MenuSearch> |
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.
Would depend how common this is (having a non-menu item content above the menu that isn't a search input), but in this instance I feel like MenuSearch/MenuSearchInput aren't really accurate for the context.
For something like this I wonder if a MenuHeader would be better (since we do already have a MenuFooter), then maybe MenuSearch/MenuSearchInput could be placed inside of that.
This isn't a blocker since it'd require some discussion and doesn't pertain to the original issue.
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.
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.
Yeah, I can see an argument for calling this a header where you can place a search input and potentially other things.
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 agree, I like MenuHeader and also agree with @thatblindgeye below that it can be done in another issue.
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.
For the linked issue this looks good. We can always open a followup regarding the convo above.
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.
@kmcfaul can you open a follow up issue please. And we can mere this PR
Opened #8933 as a follow up for the MenuSearch > MenuHeader discussion |
What: Closes #8187
MenuInput
toMenuSearch
MenuSearchInput