-
Notifications
You must be signed in to change notification settings - Fork 994
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
Fixes #37746 - Update to pf5 #10272
base: develop
Are you sure you want to change the base?
Fixes #37746 - Update to pf5 #10272
Conversation
d0f6fed
to
1e2fd6f
Compare
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.
Except for a few small things I commented on (and some not successful checks), everything looks fine, thank you! 🥳
webpack/assets/javascripts/react_app/components/HostDetails/Audits/index.js
Outdated
Show resolved
Hide resolved
webpack/assets/javascripts/react_app/components/HostDetails/DetailsCard/index.js
Outdated
Show resolved
Hide resolved
...ssets/javascripts/react_app/components/HostDetails/Tabs/Details/Cards/TemplatesCard/index.js
Outdated
Show resolved
Hide resolved
...assets/javascripts/react_app/components/HostDetails/Templates/CardItem/CardTemplate/index.js
Outdated
Show resolved
Hide resolved
...sets/javascripts/react_app/components/Layout/components/TaxonomySwitcher/TaxonomyDropdown.js
Show resolved
Hide resolved
webpack/assets/javascripts/react_app/components/PF4/TableIndexPage/Table/Table.js
Outdated
Show resolved
Hide resolved
webpack/assets/javascripts/react_app/components/SearchBar/SearchAutocomplete.js
Outdated
Show resolved
Hide resolved
return [ | ||
isDeleteable && { | ||
title: __('Delete'), | ||
onClick: () => onDeleteClick({ id, name }), | ||
isDisabled: !canDelete, | ||
isAriaDisabled: !canDelete, | ||
}, | ||
...((getActions && | ||
getActions({ id, name, canDelete, canEdit, ...item })) ?? | ||
[]), | ||
...extendActions.map(action => ({ | ||
...action, | ||
isAriaDisabled: action.isDisabled, | ||
})), | ||
].filter(Boolean); | ||
}; |
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.
Fixed both, thanks
Thanks @kmalyjur for the review, all should be fixed now. I'll open a seperate PR for host page
|
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.
Thank you! I'm just not sure about some of the not-passing checks, but I'm certain you'll figure it out :)
@@ -281,6 +281,7 @@ const HostsIndex = () => { | |||
window.location.href = foremanUrl(`/hosts/${id}/clone`); | |||
}, | |||
isDisabled: !canEdit, | |||
autoFocus: true, |
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.
Need to remove
The checks are mostly failing due to this PR not having the correct foreman-js version, which will only be available once the foreman-js PR is merged. and also will need to do a packaging PR |
23a04ac
to
4339a09
Compare
Functionally this has been working well on foreman and katello pages..Ack on this outside of dependency related CI issues.. |
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.
The pages are loading correctly and all the pages look good from everything I tested..Changes make sense for the upgrade..Ack.. 👍🏼
Updated PR to include new components that were added in the last 5 months |
"tabbable": "~5.2.0", | ||
"tabbable": "^6.2.0", |
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.
Note to self: this doesn't need packaging.
"@patternfly/patternfly": "^5.1.0", | ||
"@patternfly/react-charts": "^7.3.0", | ||
"@patternfly/react-core": "^5.1.1", | ||
"@patternfly/react-icons": "^5.1.1", | ||
"@patternfly/react-styles": "^5.1.1", | ||
"@patternfly/react-table": "^5.1.1", | ||
"@patternfly/react-tokens": "^5.1.1", |
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.
@MariaAga do you need help packaging those?
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.
or will it be vendored inside foreman-js
and we won't need packaging these separately?
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.
It will be inside foreman-js
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.
okay, so the change here is just temporarily until there is a foreman-js release out with those changes? and we don't package tabbable
, so you technically don't need any packaging ACK ;-)
(GH will still want it, so, once there is a foreman-js release out, and the version requirement was bumped here, you get it)
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.
Yes, thanks
@theforeman/packaging |
Do I get it right that this adds patternfly 5, but doesn't remove any older version? So now we have yet another front end framework in place? |
Nope, it removes it in foreman-js "Needs theforeman/foreman-js#481 & to remove pf5 from package.json" |
Needs theforeman/foreman-js#481 & to remove pf5 from package.json
Will need plugin updates as well.
For testing with the foreman-js PR, you will need to add
to
foreman/package.json
foreman and foreman-js need to be in the pf5 branch
in the foreman dir bundle exec rake assets:clobber rm -rf public/webpack node_modules package-lock.json npm i --legacy-peer-deps
in the foreman-js npm run clean npm i --legacy-peer-deps NODE_OPTIONS=--openssl-legacy-provider npm run build npm run link
and then in the foreman dir bundle exec foreman start (or start webpack )