Skip to content

Conversation

@gitdallas
Copy link
Contributor

@gitdallas gitdallas commented May 17, 2023

Closes #9128

Possibly closes or atleast makes effort towards #9116 . I replaced hard coded classes in instances that the style object had one to match.

@patternfly-build
Copy link
Contributor

patternfly-build commented May 17, 2023

@wise-king-sullyman
Copy link
Contributor

image

Should these be changed?

@wise-king-sullyman
Copy link
Contributor

Primary detail icons are still off. This PR is left, v4 is right. Is this change expected?
image

@tlabaj tlabaj requested a review from mcoker May 17, 2023 20:28
Copy link
Contributor

@wise-king-sullyman wise-king-sullyman left a comment

Choose a reason for hiding this comment

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

I'm still curious about my previous questions, but I wouldn't block for either of them.

@gitdallas
Copy link
Contributor Author

@wise-king-sullyman Ah - I think I just searched the react-core/component dir.. I'll see if I can update those real quick and see what's going on with the icons.

@gitdallas
Copy link
Contributor Author

gitdallas commented May 17, 2023

@mcoker @srambach @mattnolting

any idea about the spacing of icons? for v5 i'm seeing https://patternfly-react-v5.surge.sh/patterns/primary-detail/react-demos/primary-detail-full-page/ :
image

and for v4 i'm seeing https://www.patternfly.org/v4/demos/primary-detail/react-demos/primary-detail-full-page/ :
image

the v5 margin-right is coming up as nothing

@mcoker
Copy link
Contributor

mcoker commented May 17, 2023

@gitdallas @wise-king-sullyman nice find! That's a bug in core - your update looks good to me. I created a core issue to fix that, no react follow up should be needed patternfly/patternfly#5591

@gitdallas
Copy link
Contributor Author

@mcoker if you could give an approval with your "approval", that'd be great 😆

@tlabaj
Copy link
Contributor

tlabaj commented May 18, 2023

@gitdallas @wise-king-sullyman nice find! That's a bug in core - your update looks good to me. I created a core issue to fix that, no react follow up should be needed patternfly/patternfly#5591

@mcoker that is a PR approval correct?

Copy link
Contributor

@mcoker mcoker left a comment

Choose a reason for hiding this comment

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

LGTM! I see some others that should probably be updated, too? But looks like they're all example things, so no rush for release candidate.

Components

packages/react-core//src/components/MenuToggle/examples/MenuToggle.css:#ws-react-c-menu-toggle-primary .pf-c-menu-toggle, #ws-react-c-menu-toggle-secondary .pf-c-menu-toggle {
packages/react-core//src/components/Alert/examples/alert.css:.ws-react-c-alert .pf-c-alert {
packages/react-core//src/components/Checkbox/examples/checkbox.css:.ws-react-c-checkbox .pf-c-check.nested {
packages/react-core//src/demos/JumpLinks.md:    const masthead = document.getElementsByClassName('pf-c-masthead')[0];
packages/react-core//src/demos/examples/JumpLinks/JumpLinksWithDrawer.js:    const masthead = document.getElementsByClassName('pf-c-masthead')[0];

Layouts

packages/react-core//src/layouts/Split/examples/split.css:.ws-react-l-split .pf-l-split,
packages/react-core//src/layouts/Split/examples/split.css:.ws-react-l-split .pf-l-split > .pf-l-split__item {
packages/react-core//src/layouts/Gallery/examples/gallery.css:.ws-react-l-gallery .pf-l-gallery {
packages/react-core//src/layouts/Gallery/examples/gallery.css:.ws-react-l-gallery .pf-l-gallery > div {
packages/react-core//src/layouts/Bullseye/examples/bullseye.css:.ws-react-l-bullseye .pf-l-bullseye,
packages/react-core//src/layouts/Bullseye/examples/bullseye.css:.ws-react-l-bullseye .pf-l-bullseye > div {
packages/react-core//src/layouts/Level/examples/level.css:.ws-react-l-level .pf-l-level {
packages/react-core//src/layouts/Level/examples/level.css:.ws-react-l-level .pf-l-level,
packages/react-core//src/layouts/Level/examples/level.css:.ws-react-l-level .pf-l-level > div {
packages/react-core//src/layouts/Stack/examples/stack.css:.ws-react-l-stack > .pf-l-stack {
packages/react-core//src/layouts/Stack/examples/stack.css:.ws-react-l-stack .pf-l-stack,
packages/react-core//src/layouts/Stack/examples/stack.css:.ws-react-l-stack .pf-l-stack > .pf-l-stack__item {
packages/react-core//src/layouts/Flex/__tests__/Flex.test.tsx:            .className.replace('pf-l-flex', '')
packages/react-core//src/layouts/Flex/examples/flex.css:.ws-react-l-flex .pf-l-flex {
packages/react-core//src/layouts/Flex/examples/flex.css:.ws-react-l-flex .pf-l-flex > div,
packages/react-core//src/layouts/Grid/examples/grid.css:.ws-react-l-grid > .pf-l-grid,
packages/react-core//src/layouts/Grid/examples/grid.css:.ws-react-l-grid > .pf-l-grid > .pf-l-grid__item {
packages/react-core//src/demos/CardDemos.md:                          <div className="pf-l-flex__item">100C</div>
packages/react-core//src/demos/CardDemos.md:                          <div className="pf-l-flex__item">50C</div>
packages/react-core//src/demos/CardDemos.md:                          <div className="pf-l-flex__item">0C</div>
packages/react-core//src/demos/CardDemos.md:                          <div className="pf-l-flex__item">3.6Ghz</div>
packages/react-core//src/demos/CardDemos.md:                          <div className="pf-l-flex__item">1.5Ghz</div>
packages/react-core//src/demos/CardDemos.md:                          <div className="pf-l-flex__item">0GHZ</div>
packages/react-core//src/demos/CardDemos.md:                          <div className="pf-l-flex__item">100C</div>
packages/react-core//src/demos/CardDemos.md:                          <div className="pf-l-flex__item">50C</div>
packages/react-core//src/demos/CardDemos.md:                          <div className="pf-l-flex__item">0C</div>
packages/react-core//src/demos/CardDemos.md:                          <div className="pf-l-flex__item">3.6Ghz</div>
packages/react-core//src/demos/CardDemos.md:                          <div className="pf-l-flex__item">1.5Ghz</div>
packages/react-core//src/demos/CardDemos.md:                          <div className="pf-l-flex__item">0GHZ</div>
packages/react-core//src/demos/CardDemos.md:                          <div className="pf-l-flex__item">100C</div>
packages/react-core//src/demos/CardDemos.md:                          <div className="pf-l-flex__item">50C</div>
packages/react-core//src/demos/CardDemos.md:                          <div className="pf-l-flex__item">0C</div>
packages/react-core//src/demos/CardDemos.md:                          <div className="pf-l-flex__item">3.6Ghz</div>
packages/react-core//src/demos/CardDemos.md:                          <div className="pf-l-flex__item">1.5Ghz</div>
packages/react-core//src/demos/CardDemos.md:                          <div className="pf-l-flex__item">0GHZ</div>
packages/react-core//src/demos/CardDemos.md:                          <div className="pf-l-flex__item">100C</div>
packages/react-core//src/demos/CardDemos.md:                          <div className="pf-l-flex__item">50C</div>
packages/react-core//src/demos/CardDemos.md:                          <div className="pf-l-flex__item">0C</div>
packages/react-core//src/demos/CardDemos.md:                          <div className="pf-l-flex__item">3.6Ghz</div>
packages/react-core//src/demos/CardDemos.md:                          <div className="pf-l-flex__item">1.5Ghz</div>
packages/react-core//src/demos/CardDemos.md:                          <div className="pf-l-flex__item">0GHZ</div>
packages/react-core//src/demos/CardDemos.md:                          <div className="pf-l-flex__item">100C</div>
packages/react-core//src/demos/CardDemos.md:                          <div className="pf-l-flex__item">50C</div>
packages/react-core//src/demos/CardDemos.md:                          <div className="pf-l-flex__item">0C</div>
packages/react-core//src/demos/CardDemos.md:                          <div className="pf-l-flex__item">3.6Ghz</div>
packages/react-core//src/demos/CardDemos.md:                          <div className="pf-l-flex__item">1.5Ghz</div>
packages/react-core//src/demos/CardDemos.md:                          <div className="pf-l-flex__item">0GHZ</div>
packages/react-core//src/demos/CardDemos.md:                          <div className="pf-l-flex__item">100C</div>
packages/react-core//src/demos/CardDemos.md:                          <div className="pf-l-flex__item">50C</div>
packages/react-core//src/demos/CardDemos.md:                          <div className="pf-l-flex__item">0C</div>
packages/react-core//src/demos/CardDemos.md:                          <div className="pf-l-flex__item">3.6Ghz</div>
packages/react-core//src/demos/CardDemos.md:                          <div className="pf-l-flex__item">1.5Ghz</div>
packages/react-core//src/demos/CardDemos.md:                          <div className="pf-l-flex__item">0GHZ</div>

@nicolethoen
Copy link
Contributor

@mcoker @tlabaj
i opened a follow up issue and added it to the clean up examples/demo epic on the roadmap

@tlabaj tlabaj self-requested a review May 18, 2023 13:46
Copy link
Contributor

@tlabaj tlabaj left a comment

Choose a reason for hiding this comment

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

@dlabrecq does this will need to be updated correct? I can open a follow up to this PR.

@dlabrecq
Copy link
Member

dlabrecq commented May 18, 2023

@tlabaj charts uses tokens, so snapshots will need updating. However, the only "pf-" prefixes are for a couple keys and a chart pattern ID.

Copy link
Contributor

@tlabaj tlabaj left a comment

Choose a reason for hiding this comment

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

It looks like some updates are needed in react-styles and anywhere those classes are being pulled in. the classes her are still using pf-c prefix. The Popper should at least be updated here and we can follow up with the rest. They may require some investigation.
https://github.com/patternfly/patternfly-react/tree/v5/packages/react-styles/src/css/components

@mcoker
Copy link
Contributor

mcoker commented May 18, 2023

re: the react-styles updates @tlabaj mentioned, I'm not sure where the names for the color vars are coming from - https://github.com/patternfly/patternfly-react/blob/v5/packages/react-styles/src/css/components/Table/inline-edit.css

We don't have a --global--[color]--number CSS var in core, though it looks like that is how the vars were defined before we added the v5 prefix, too - 3879fc7#diff-d99fb7d33fdb9c29c555e2926969439a2857b3ec7e95c13155c6c21bb3dce1e2

I can't find an editable table example using composable table, but I see the legacy table example - https://www.patternfly.org/v4/components/table/react-legacy#editable-rows. It doesn't look like any of the classnames in https://github.com/patternfly/patternfly-react/blob/v5/packages/react-styles/src/css/components/Table/inline-edit.css are being applied in edit mode.

If those colors still need to be applied, --pf-v5-global--[color]--[number] should be --pf-v5-global--palette--[color]-[number] - and the color names should be lower-case.

@nicolethoen
Copy link
Contributor

@tlabaj I think that can be a follow up issue because there are lots of other problems with that CSS.

@tlabaj
Copy link
Contributor

tlabaj commented May 18, 2023

@tlabaj charts uses tokens, so snapshots will need updating. However, the only "pf-" prefixes are for a couple keys and a chart pattern ID.

@dlabrecq sorry i forgot to paste a link to what I was talking about above. I assume this is what needs to be updated correct?
https://github.com/patternfly/patternfly-react/blob/v5/packages/react-charts/src/components/ChartUtils/chart-helpers.ts

Copy link
Contributor

@mcoker mcoker left a comment

Choose a reason for hiding this comment

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

popper class lgtm 👍

@tlabaj
Copy link
Contributor

tlabaj commented May 18, 2023

Here is a list of issues that will be follow ups to this PR
#9144, #9150, #9151

@tlabaj tlabaj merged commit 8fbd940 into patternfly:v5 May 18, 2023
nicolethoen added a commit to Kells512/patternfly-react that referenced this pull request Sep 1, 2023
* fix(Multiple): update old component classnames

* update cypress test selectors

* fix cypress selectors

* fix cypress selectors

* update some code-editor/deprecated/table/integration directories

* update popper css

---------

Co-authored-by: nicolethoen <nthoen@redhat.com>
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.

Bug - Menu -Spacing issue regression with checkbox menu

8 participants