Skip to content
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

CONSOLE-3081: moved imports #11370

Merged

Conversation

mattnolting
Copy link
Contributor

There's a bug in MiniCssExtractPlugin that misorders css imports. To resolve this, it appears that .scss imported in app.jsx AFTER other imports works as expected, but to ensure that dark theme imports are correctly ordered, it's most reliable to use .css (MiniCssExtractPlugin does not seem to present this issue with .css files).

@@ -61,6 +61,7 @@ const NOTIFICATION_DRAWER_BREAKPOINT = 1800;
// Edge lacks URLSearchParams
import 'url-search-params-polyfill';
import { graphQLReady } from '../graphql/client';
import '@patternfly/patternfly/patternfly-theme-dark.scss'; // load dark theme here as MiniCssExtractPlugin ignores load order of sass and dark theme must load after all other css
Copy link
Member

Choose a reason for hiding this comment

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

Can this go on line 55 so it's with the other (s)css?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yes, if line 57 can move to line 52, above the css imports

Copy link
Member

Choose a reason for hiding this comment

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

Sure. The goal is to keep things grouped.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

@rhamilto updated

@openshift-ci openshift-ci bot added the needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. label Apr 20, 2022
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Apr 20, 2022

Hi @mattnolting. Thanks for your PR.

I'm waiting for a openshift member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@openshift-ci openshift-ci bot added the component/core Related to console core functionality label Apr 20, 2022
@rhamilto
Copy link
Member

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Apr 20, 2022
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Apr 20, 2022

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: mattnolting, rhamilto

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Apr 20, 2022
@spadgett
Copy link
Member

I have a feeling this is due to ignoreOrder in the plugin configuration, but that might be difficult to remove:

https://github.com/openshift/console/blob/master/frontend/webpack.config.ts#L39

@jcaianirh
Copy link
Member

jcaianirh commented Apr 26, 2022

QE Approver:
/assign @yapei

@jcaianirh
Copy link
Member

/ok-to-test

@openshift-ci openshift-ci bot added ok-to-test Indicates a non-member PR verified by an org member that is safe to test. and removed needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Apr 26, 2022
@jcaianirh
Copy link
Member

/label docs-approved
/label px-approved

We have docs- and px-approval for the epic.

@openshift-ci openshift-ci bot added docs-approved Signifies that Docs has signed off on this PR px-approved Signifies that Product Support has signed off on this PR labels Apr 26, 2022
@yapei
Copy link
Contributor

yapei commented Apr 27, 2022

@yanpzhan will test the PR

@yanpzhan
Copy link
Contributor

@mattnolting Launched a cluster against the pr, about white box mentioned in #11384 (comment), still found on the cluster:
Screenshot from 2022-04-27 12-11-07
Will it be fix in this pr?

@mattnolting
Copy link
Contributor Author

@mattnolting Launched a cluster against the pr, about white box mentioned in #11384 (comment), still found on the cluster:

Screenshot from 2022-04-27 12-11-07

Will it be fix in this pr?

@yanpzhan No, #11384 converts this component to a PF toggle group. For the toggle group to appear correctly in @sg00dwin's PR, this PR will need to be merged.

@yanpzhan
Copy link
Contributor

@mattnolting Thanks for your info.
/label qe-approved

@openshift-ci openshift-ci bot added the qe-approved Signifies that QE has signed off on this PR label Apr 27, 2022
@rhamilto
Copy link
Member

/retest

@openshift-bot
Copy link
Contributor

/retest-required

Please review the full test history for this PR and help us cut down flakes.

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Apr 27, 2022

@mattnolting: all tests passed!

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. component/core Related to console core functionality docs-approved Signifies that Docs has signed off on this PR lgtm Indicates that a PR is ready to be merged. ok-to-test Indicates a non-member PR verified by an org member that is safe to test. px-approved Signifies that Product Support has signed off on this PR qe-approved Signifies that QE has signed off on this PR
Projects
None yet
Development

Successfully merging this pull request may close these issues.

10 participants