-
Notifications
You must be signed in to change notification settings - Fork 29
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
base: main
Are you sure you want to change the base?
Conversation
lgtm! can we add a cypress test as well, just to keep inline with the rest of the components. |
@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. |
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 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>} |
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.
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.
@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? |
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. |
@edonehoo suggested for naming ideas:
Curious about people's opinions. I think I like 'view manager' the best? |
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. |
For RHCLOUD-40372. A preview can be see in the comment below.