-
Story
-
Resolution: Done
-
Major
-
None
-
12
-
False
-
-
False
-
subs-swatch
-
https://github.com/RedHatInsights/curiosity-frontend/pull/1626, https://github.com/RedHatInsights/curiosity-frontend/pull/1629, https://github.com/RedHatInsights/curiosity-frontend/pull/1634, https://github.com/RedHatInsights/curiosity-frontend/pull/1630, https://github.com/RedHatInsights/curiosity-frontend/pull/1660, https://github.com/RedHatInsights/curiosity-frontend/pull/1664
-
-
As a developer I need to apply the Patternfly 6 packages to the UI
Acceptance criteria
- Update NPM packages, and related consoledot packages that may be affected
- Update, correct, remove any existing styles. This will also include realigning the global colors used.
- Update any related component props, or removed/replaced components
Assumptions and questions
- This involves running the codemods, and related styling and class fixes to update components at a base level. Linting will still need to be resolved
- Styling is the biggest issue. The styling mod will replace some of the global variables we're using, mostly spacing adjustments around the graphs. But we'll need to make a determination about moving to the new pf tokens for colors. For context every PF update has caused a similar issue, with the move from PF4 to 5 being the easiest (this includes the comparison from our prep from 5 to 6)