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(Menu): match css structure #8820

Merged
merged 2 commits into from Apr 10, 2023
Merged

feat(Menu): match css structure #8820

merged 2 commits into from Apr 10, 2023

Conversation

kmcfaul
Copy link
Contributor

@kmcfaul kmcfaul commented Mar 16, 2023

What: Closes #8187

  • Renames MenuInput to MenuSearch
  • Adds MenuSearchInput

@patternfly-build
Copy link
Contributor

patternfly-build commented Mar 16, 2023

Copy link
Contributor

@thatblindgeye thatblindgeye left a 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.

Comment on lines +130 to +132
<MenuSearch>
<MenuSearchInput>Unselectable text displayed at the top of the menu</MenuSearchInput>
</MenuSearch>
Copy link
Contributor

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.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

@mcoker @mcarrano

Right now it's matching the css class naming but I agree that Header may be more usefully generic.

Copy link
Member

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.

Copy link
Member

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.

Copy link
Contributor

@thatblindgeye thatblindgeye left a 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.

Copy link
Contributor

@tlabaj tlabaj left a 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

@kmcfaul
Copy link
Contributor Author

kmcfaul commented Apr 10, 2023

Opened #8933 as a follow up for the MenuSearch > MenuHeader discussion

@tlabaj tlabaj merged commit 9b64ccf into patternfly:v5 Apr 10, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Menu - filter/search naming and markup, props
7 participants