-
Notifications
You must be signed in to change notification settings - Fork 64
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
fix(snapshot): add test pipelinerun list and capitalize breadcrumbs #847
fix(snapshot): add test pipelinerun list and capitalize breadcrumbs #847
Conversation
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## main #847 +/- ##
==========================================
+ Coverage 85.59% 85.67% +0.07%
==========================================
Files 596 596
Lines 15041 15046 +5
Branches 4214 4217 +3
==========================================
+ Hits 12875 12890 +15
+ Misses 2029 2020 -9
+ Partials 137 136 -1
... and 1 file with indirect coverage changes Continue to review full report in Codecov by Sentry.
|
c7c149f
to
b648167
Compare
Is Type being lowercase in the filter selector coming from data, or our code? Other areas we're filtering on PLR type, it shows as capitalized (Build, Test). |
/retest |
b648167
to
b78ff9a
Compare
@mattreid we get it as lowercase types from the object metadata. I updated to capitalize it while displaying |
@@ -147,7 +147,7 @@ const SnapshotDetailsView: React.FC<SnapshotDetailsViewProps> = ({ | |||
<> | |||
<StatusIconWithTextLabel | |||
key={env.metadata?.name} | |||
text={env.metadata.name} | |||
text={capitalize(env.metadata.name)} |
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 is a env.spec?.displayName
optional field in Environment CR, We must use that if exists or else fallback to the env.metadata.name. This way we will be be respecting the user's choice of displayName rather than Capitalizing the K8s resource name.
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.
Deployment tab uses the above approach, so the Development
text comes from spec.displayName and notice the other environment which doesn't have displayName and it uses resource name. Can we stick to this displayName or resource.name (without captializing) approach for consistency ? cc: @mattreid
b78ff9a
to
9d631f8
Compare
@@ -108,7 +109,7 @@ const SnapshotOverviewTab: React.FC<SnapshotOverviewTabProps> = ({ | |||
<Link | |||
to={`/application-pipeline/workspaces/${workspace}/applications/${snapshot.spec.application}/deployments`} | |||
> | |||
{env} | |||
{capitalize(env)} |
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 should use environment's spec.displayName here as well. 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.
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.
Looking good, but looks like we need more tests to satisfy codecov
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: abhinandan13jan, rottencandy The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
a8a3c0b
to
fbe6316
Compare
New changes are detected. LGTM label has been removed. |
13c47d0
to
5939ce9
Compare
/retest |
cda0275
to
35c31ca
Compare
35c31ca
to
8172a95
Compare
fix(snapshot): add test plrs, capitalize breadcrumb and environment
8172a95
to
c814c03
Compare
/retest |
@abhinandan13jan: 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. |
Fixes
https://issues.redhat.com/browse/RHTAPBUGS-839
Description
Type of change
Screen shots / Gifs for design review
How to test or reproduce?
Browser conformance: