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
Bug 1797149: fix inconsistencies in topology node styling #4117
Bug 1797149: fix inconsistencies in topology node styling #4117
Conversation
b9f4f59
to
1509a00
Compare
@@ -10,7 +8,7 @@ import { | |||
} from '@console/topology'; | |||
import { modelFor, referenceFor } from '@console/internal/module/k8s'; | |||
import { useAccessReview } from '@console/internal/components/utils'; | |||
import { getTopologyFilters, TopologyFilters } from '../../filters/filter-utils'; | |||
import { TopologyFilters } from '../../filters/filter-utils'; |
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 can be removed along with the optional filters
prop
1509a00
to
3bdd717
Compare
3bdd717
to
8d2aa1b
Compare
8d2aa1b
to
e9127c5
Compare
@christianvogt: This pull request references Bugzilla bug 1797149, which is valid. The bug has been moved to the POST state. The bug has been updated to refer to the pull request using the external bug tracker. In response to this:
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. |
e9127c5
to
5fce990
Compare
@christianvogt: This pull request references Bugzilla bug 1797149, which is valid. In response to this:
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. |
1 similar comment
@christianvogt: This pull request references Bugzilla bug 1797149, which is valid. In response to this:
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. |
&__bg { | ||
fill: #d1d1d1; | ||
fill-opacity: 0.5; | ||
stroke: #bbbbbb; |
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 use #d1d1d1
and #bbbbb
in the three groups' styles. Could we add these as variables in the topology-utils.scss
?
cursor: grab; | ||
} | ||
|
||
fill: var(--pf-global--Color--300); | ||
& text { | ||
fill: #fff; |
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.
while we're in here
fill: #fff; | |
fill: var(--pf-global--Color--light-100); |
'is-filtered': filtered, | ||
'is-dragging': dragging, | ||
})} | ||
className="odc-base-node__label" | ||
x={x + width / 2} | ||
y={y + height + 20} |
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.
Other groupings use 30 here. Maybe a constant or default value in SvgBoxedText
? (paddingX, paddingY, and truncate as well?)
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.
Let's improve this as part of a PR to to fix the label padding.
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.
@christianvogt did you end up doing the 24px between components/groupings and their label?
@serenamarie125 that's not part of this PR. I focused on node state styles. I think we're better off doing a followup PR for any further styling issues as this PR is already large enough. |
/retest |
5fce990
to
c842718
Compare
@@ -1,8 +1,7 @@ | |||
.odc-base-edge.odc-event-source-link { | |||
--edge--stroke: #bbbbbb; |
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.
Maybe $edge-stroke-color
@@ -1,8 +1,6 @@ | |||
.odc-base-edge.odc-traffic-link { | |||
--edge--stroke-width: 0; | |||
--edge--stroke: #bbbbbb; |
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.
ditto
c842718
to
ce23d77
Compare
@jeff-phillips-18 added a new variable |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: christianvogt, jeff-phillips-18 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 |
/retest |
@christianvogt: All pull requests linked via external trackers have merged. Bugzilla bug 1797149 has been moved to the MODIFIED state. In response to this:
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. |
Fixes:
Fixes https://issues.redhat.com/browse/ODC-2903
Analysis / Root cause:
There is a lot of similar code across the various react components representing the nodes and groups in topology. Unfortunately this is error prone as we've added new states and new react components and some of them simply aren't done in a consistent manner.
Solution Description:
Went through each topology node and group and updated the styles for consistent naming and css rule specificity.
Requires a future run through with @openshift/team-devconsole-ux to ensure colors are all correct. At least now the styles are consistent across nodes.
Screen shots / Gifs for design review:
selected:
find:
Browser conformance: