Skip to content

Add drag drop column component #766

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

Open
wants to merge 9 commits into
base: main
Choose a base branch
from

Conversation

apinkert
Copy link

For RHCLOUD-40372. A preview can be see in the comment below.

@patternfly-build
Copy link

patternfly-build commented Jul 28, 2025

@aferd
Copy link
Collaborator

aferd commented Jul 31, 2025

lgtm! can we add a cypress test as well, just to keep inline with the rest of the components.

@apinkert
Copy link
Author

apinkert commented Aug 4, 2025

@aferd do you know if the cypress component tests are actually being used? I can't get them to run locally (and it doesn't look like the cypress component tests are part of the test_cypress check below) but I don't have an issue running the one cypress e2e test.

Copy link
Contributor

@nicolethoen nicolethoen left a comment

Choose a reason for hiding this comment

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

I am confused about the relationship between this new component and the existing ColumnManagementModal. Can the documentation and file structure of these components be combined?

I think the ColumnManagementModal should be leveraging this ColumnManagement component under the hood. And they should not be separate nav items.

return (
<>
<Title headingLevel="h3">{title}</Title>
{description && <div style={{ paddingBottom: '1rem' }}><p>{description}</p></div>}
Copy link
Contributor

Choose a reason for hiding this comment

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

Instead of hardcoding styles here to create the margin you'd like, i'd recommend className='pf-v6-u-mb-md'

or even better yet, the title and description should be left off. This could be placed in the body of a Modal or other container which can handle the title.

@karelhala
Copy link
Collaborator

@nicolethoen we didn't wanted to remove the ColumnManagementModal implementation, but because it's not really surfaced anywhere we could add another example in the ColumnManagement component with modal example and remove the ColumnManagementModal 🤔 Do you want @apinkert to do it in this PR or seperate one?

@nicolethoen
Copy link
Contributor

I like the idea of the ColumnManagement component being something that can be dropped into a Modal and doing that in our docs in lieu of the preexisting ColumnManagementModal component.

It looks like 4 products are currently using the ColumnManagementModal according to PF analytics reports, so we cannot outright move it, but we could remove it from the docs - or mark it deprecated in the short term.

I wonder if the component name (and relevant props) should use a different term other than ColumnManagement, since this component could be used for any sort of list management - like nav items. I've asked our designers if they have an opinion about the name.

@nicolethoen
Copy link
Contributor

@edonehoo suggested for naming ideas:

  • Display manager / editor
  • List manager
  • View manager
  • Layout manager / Component layout manager (might get confused with our actual Layouts)

Curious about people's opinions. I think I like 'view manager' the best?

@apinkert
Copy link
Author

apinkert commented Aug 6, 2025

I like List or View Manager personally, but don't have a strong preference! I think renaming this component makes sense in the context of this PR, and dropping it into the Column Management Modal should be a separate PR.

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.

5 participants