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 1875809: Restyle Time to inlineblock for Topology - Pipeline & Builds #6493
Bug 1875809: Restyle Time to inlineblock for Topology - Pipeline & Builds #6493
Conversation
@@ -0,0 +1,5 @@ | |||
.pipeline-run-item { |
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.
.pipeline-run-item { | |
.odc-pipeline-run-item { |
@@ -31,7 +32,11 @@ const PipelineRunItem: React.FC<PipelineRunItemProps> = ({ pipelineRun }) => { | |||
<Grid hasGutter> |
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.
The li
one line up could use with the odc-pipeline-run-item
class too to maintain a good structure.
@@ -9,6 +9,10 @@ | |||
align-items: center; | |||
} | |||
|
|||
.build-overview__item-time { |
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 think we can probably leave the build class alone without the prefix... it's older code and appears to be more consistent with what is there.
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 think something got lost in translation here @abhinandan13jan haha... I didn't mean undo this change, I was merely saying don't change .build-overview__item-time
to meet my other change request. We definitely still want to apply this to Builds (I'm not contradicting myself from the previous time you asked about addressing the Build Config section -- we still definitely want to keep this functionality consistent).
e0afd1c
to
7b048cf
Compare
@abhinandan13jan: This pull request references Bugzilla bug 1875809, which is valid. The bug has been moved to the POST state. 3 validation(s) were run on this bug
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. |
/kind bug |
@andrewballantyne updated |
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.
The Pipeline section changes look good ... please return the changes for the Build section. Apologizes for the misunderstanding.
7b048cf
to
de4be08
Compare
/test frontend |
/retest |
/lgtm |
{lastUpdated && <span className="text-muted"> ({fromNow(lastUpdated)})</span>} | ||
{lastUpdated && ( | ||
<span className="odc-pipeline-run-item__time text-muted"> | ||
({fromNow(lastUpdated)}) |
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 shouldn't be using
anymore because when the time wraps, it creates an unwanted space offset at the beginning of the line.
You can see this in the description screenshot.
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.
removed nbsp from both Pipeline and Build
de4be08
to
1c17312
Compare
{lastUpdated && ( | ||
<span className="odc-pipeline-run-item__time text-muted">({fromNow(lastUpdated)})</span> | ||
)} |
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.
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.
Doesn't work with the space, it gets trimmed off. I tried to achieve the behavior by using a right-padding on previous element.
Let me know if that's fine.
@@ -44,8 +44,10 @@ const BuildOverviewItem: React.SFC<BuildOverviewListItemProps> = ({ build }) => | |||
Build | |||
<BuildNumberLink build={build} /> | |||
| |||
{conjugateBuildPhase(phase)} | |||
{lastUpdated && <span className="text-muted"> ({fromNow(lastUpdated)})</span>} | |||
<span className="build-overview__item-phase">{conjugateBuildPhase(phase)}</span> |
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.
What about doing this:
<div>
Build <BuildNumberLink build={build} /> {conjugateBuildPhase(phase)}
{lastUpdated && (
<>
{' '}
<span className="build-overview__item-time text-muted">({fromNow(lastUpdated)})</span>
</>
)}
</div>
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.
Updated for both Builds and Pipelines
8ba8b88
to
3e0fa8b
Compare
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: abhinandan13jan, andrewballantyne, christianvogt 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 |
@abhinandan13jan: All pull requests linked via external trackers have merged: Bugzilla bug 1875809 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. |
Issue
https://issues.redhat.com/browse/ODC-4455
Solution
Fixed in two different commits
Screenshot
Tests
No tests altered
Browser conformance
Chrome & Firefox