-
Notifications
You must be signed in to change notification settings - Fork 43
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
✨ Migration to PF V5 #1078
✨ Migration to PF V5 #1078
Conversation
@ibolton336 for certain components that had major changes, they released them early under |
Signed-off-by: Gilles Dubreuil <gdubreui@redhat.com>
Signed-off-by: Gilles Dubreuil <gdubreui@redhat.com>
Signed-off-by: Gilles Dubreuil <gdubreui@redhat.com>
Signed-off-by: Gilles Dubreuil <gdubreui@redhat.com>
Signed-off-by: Gilles Dubreuil <gdubreui@redhat.com>
Signed-off-by: Gilles Dubreuil <gdubreui@redhat.com>
Signed-off-by: Gilles Dubreuil <gdubreui@redhat.com>
Signed-off-by: Gilles Dubreuil <gdubreui@redhat.com>
Signed-off-by: Gilles Dubreuil <gdubreui@redhat.com>
Signed-off-by: Gilles Dubreuil <gdubreui@redhat.com>
Signed-off-by: Gilles Dubreuil <gdubreui@redhat.com>
Signed-off-by: Mike Turley <mike.turley@alum.cs.umass.edu>
Signed-off-by: Mike Turley <mike.turley@alum.cs.umass.edu> Signed-off-by: Gilles Dubreuil <gdubreui@redhat.com>
Signed-off-by: Gilles Dubreuil <gdubreui@redhat.com>
Signed-off-by: Gilles Dubreuil <gdubreui@redhat.com>
Signed-off-by: Gilles Dubreuil <gdubreui@redhat.com>
Signed-off-by: Gilles Dubreuil <gdubreui@redhat.com>
Signed-off-by: Mike Turley <mike.turley@alum.cs.umass.edu>
Signed-off-by: Gilles Dubreuil <gdubreui@redhat.com>
Signed-off-by: Gilles Dubreuil <gdubreui@redhat.com>
Signed-off-by: Gilles Dubreuil <gdubreui@redhat.com>
Signed-off-by: Gilles Dubreuil <gdubreui@redhat.com>
Signed-off-by: Gilles Dubreuil <gdubreui@redhat.com>
Signed-off-by: Gilles Dubreuil <gdubreui@redhat.com>
Signed-off-by: Gilles Dubreuil <gdubreui@redhat.com>
Signed-off-by: Gilles Dubreuil <gdubreui@redhat.com>
Signed-off-by: Gilles Dubreuil <gdubreui@redhat.com>
Signed-off-by: Gilles Dubreuil <gdubreui@redhat.com>
Signed-off-by: Gilles Dubreuil <gdubreui@redhat.com>
Signed-off-by: Gilles Dubreuil <gdubreui@redhat.com>
Signed-off-by: Gilles Dubreuil <gdubreui@redhat.com>
Codecov ReportPatch coverage:
Additional details and impacted files@@ Coverage Diff @@
## main #1078 +/- ##
==========================================
- Coverage 46.70% 44.11% -2.60%
==========================================
Files 177 177
Lines 4462 4477 +15
Branches 1001 997 -4
==========================================
- Hits 2084 1975 -109
- Misses 2364 2491 +127
+ Partials 14 11 -3
Flags with carried forward coverage won't be shown. Click here to find out more.
☔ View full report in Codecov by Sentry. |
client/src/app/app.css
Outdated
.pf-c-icon .pf-m-default { | ||
color: var(--pf-c-icon--Color); | ||
.pf-v5-c-icon .pf-v5-m-default { | ||
color: var(--pf-v5-c-icon--Color); | ||
} | ||
|
||
.pf-c-icon.pf-m-info { | ||
color: var(--pf-c-icon--m-info--Color); | ||
.pf-v5-c-icon.pf-v5-m-info { | ||
color: var(--pf-v5-c-icon--m-info--Color); | ||
} | ||
|
||
.pf-c-icon .pf-m-success { | ||
color: var(--pf-c-icon--m-success--Color); | ||
.pf-v5-c-icon .pf-v5-m-success { | ||
color: var(--pf-v5-c-icon--m-success--Color); | ||
} | ||
|
||
.pf-c-icon .pf-m-warning { | ||
color: var(--pf-c-icon--m-warning--Color); | ||
.pf-v5-c-icon .pf-v5-m-warning { | ||
color: var(--pf-v5-c-icon--m-warning--Color); | ||
} | ||
|
||
.pf-c-icon .pf-m-danger { | ||
color: var(--pf-c-icon--m-danger--Color); | ||
.pf-v5-c-icon .pf-v5-m-danger { | ||
color: var(--pf-v5-c-icon--m-danger--Color); | ||
} |
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'm surprised that this CSS was ever necessary. I wonder if we just remove all the pf-v5-c-icon
stuff here if icons work as expected?
@gildub it looks like this was added in https://github.com/konveyor/tackle2-ui/pull/300/files#diff-acb6efd446c502574b8cfc71c2c9fda16948c4811f0040ed7efcbfd1ebdee22f, do you remember why it was needed?
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.
Thanks for point it that.
I'll check.
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.
@mturley, Effectively those classes seems unnecessary, I removed them. I can't remember why I added them in the first place.
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 haven't found any more glaring behavior regressions yet. I think this is at a point where I would be comfortable merging it as long as we make a followup effort over the next few days to thoroughly compare the before/after visually and open issues for each visual/style regression, then prioritize getting those fixed before long.
Signed-off-by: Gilles Dubreuil <gdubreui@redhat.com>
#1078 follow-up to restore personae select look and feel.
…#1104) I missed this when reviewing #1078. cc @gildub I noticed that when clicking an affected file in the drawer on the Issues pages to open the incident details modal, the last tab ("All incidents" table) was split out into its own tab bar and rendered below the contents of the selected tab. This is because of this change: https://github.com/konveyor/tackle2-ui/pull/1078/files#diff-e40974378de11be89b5b1ca02db26b8fed80482f468154ebb84807af7f0e7273L125-R147 (link takes a while to scroll the diff after loading) When I reversed the change, I saw the reason for it: the new Tabs component doesn't like to have its children expressed as a combination of an array and extra nodes (like we had been doing when mapping over the first 5 incidents and conditionally including a 6th tab). It gave this error: ![Screenshot 2023-07-10 at 3 38 00 PM](https://github.com/konveyor/tackle2-ui/assets/811963/6d10427c-15c5-47bb-973d-2110b2f2b48f) It appears to be due to this type change in PF: patternfly/patternfly-react#8217 The solution was to make sure the children of `<Tabs>` is always a single array of `<Tab>` elements. --------- Signed-off-by: Mike Turley <mike.turley@alum.cs.umass.edu>
The initial driver behind the need for PatternFly Version 5 is for the
datePicker
component which get bug fixes.But we'll need to migration to V5 anyway sooner than later.
Some components (Table, Select, Dropdown, Wizard) have a V4 version maintained in @patternfly/react-core/deprecated allowing for a smooth transition which can help us make sure there is no UX changes.
Once migrated we can progressively move to the newer components.
This PR addresses the 150+ errors initially triggered by porting to pre-release V5.
TODO (more likely in following PRs):
Tests :