-
Notifications
You must be signed in to change notification settings - Fork 667
kubevirt: add ResultTab to CreateVMWizard #2568
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
kubevirt: add ResultTab to CreateVMWizard #2568
Conversation
|
/hold |
6914d22 to
52b3730
Compare
52b3730 to
19eee49
Compare
11aa67b to
de75be1
Compare
bcbd677 to
1b820cc
Compare
97f3e1d to
80ac2ec
Compare
|
/hold cancel |
0e71be1 to
ebf41b8
Compare
frontend/packages/kubevirt-plugin/src/components/create-vm-wizard/create-vm-wizard-footer.tsx
Outdated
Show resolved
Hide resolved
| import * as classNames from 'classnames'; | ||
| import { Expandable } from '@patternfly/react-core'; | ||
|
|
||
| import './result-tab-row.scss'; |
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 have already raised following question in another PR but it was not answered.
Throughout the code, I can see import of SCSS
- like this one
- like this one but filename is prefixed with underscore
_(like it should be used via SCSS@importbut is not) - single hierarchy built via SCSS
@importinitiated bystyle.scssfor both@console/internalandkubevirt-plugin
Both cases have there pros and cons (encapsulation vs. single understandable hierarchy).
Considering we are developing an end-user application and not a reusable library, the case of a single hierarchy makes more sense to me. But I do not have a strong opinion on that as long we stay consistent.
@vojtechszocs , @rawagner , @suomiy , wdyt?
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.
my preference is to have it at the same place as the tsx file and maybe have one place for common css files
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.
This is not a blocker for this PR, so let's discuss that face to face. The point is just to be consistent.
| } | ||
|
|
||
| .kubevirt-create-vm-modal__result-tab-row--error { | ||
| background-color: #ffe6e6; |
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.
How did we get these colours? Aren't they defined by patternfly?
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.
they were taken from pf3 notification error
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.
We don't have a PF4 colour for a light red but we probably should. I can see about getting that added.
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 the dark red, let's proceed with this one and patch it later once the light red is available
ebf41b8 to
4aef50b
Compare
...packages/kubevirt-plugin/src/components/create-vm-wizard/tabs/result-tab/result-tab-row.scss
Outdated
Show resolved
Hide resolved
...packages/kubevirt-plugin/src/components/create-vm-wizard/tabs/result-tab/result-tab-row.scss
Outdated
Show resolved
Hide resolved
| @@ -0,0 +1,17 @@ | |||
| .kubevirt-create-vm-modal___result-tab-row-container { | |||
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.
Are we writing specific namespace based classes for Kubevirt? I'm trying to learn more about the general css approach, is there any documentation on this ?
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, since this component is kubevirt specific. The components are moved to core once they are used by multiple plugins. (there is some doc here)
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.
+1 thanks for that link!
|
What if we did highlighting in the YAML to show the error? (forgive this YAML content I grabbed it from a pod :) ) |
4aef50b to
630095c
Compare
We will show the appropriate errors in the list in the future as showcased here Nevertheless there might be errors where location in the yaml might be unclear.
Yup we are planning to do that. Sure we could also add YAML editing here.
It is already used here. |
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: mareklibra, suomiy The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/retest Please review the full test history for this PR and help us cut down flakes. |





depends on: