-
Notifications
You must be signed in to change notification settings - Fork 606
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
add parameters tab on PipelineRun details page #11767
Conversation
frontend/packages/pipelines-plugin/src/components/pipelineruns/PipelineRunParameters.tsx
Outdated
Show resolved
Hide resolved
<Form> | ||
<div className="co-m-pane__body"> | ||
<PipelineRunParameters fieldName="parameters" /> | ||
</div> | ||
<FormFooter | ||
handleCancel={handleCancel} | ||
cancelLabel={t('pipelines-plugin~Cancel')} | ||
hideSubmit | ||
sticky | ||
/> | ||
</Form> |
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.
In PipelineRunParameters you define all fields as read-only. Why do we need a form and cancel button on this tab?
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 initial thought was the same. Removed the Form and cancel button.
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.
@vikram-raj But there is still a PipelineRunParametersForm.tsx
and formik, this is required to fill the form fields? Then its fine for me.
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, I used Formik
to fill the form fields.
/retest |
@vikram-raj Nice! Thanks for the update. Can you also add a cypress e2e test for this? 😏 |
@jerolimov added cypress e2e tests. |
.../packages/pipelines-plugin/integration-tests/support/pages/pipelines/pipelineBuilder-page.ts
Show resolved
Hide resolved
frontend/packages/pipelines-plugin/integration-tests/features/pipelines/pipelines-runs.feature
Outdated
Show resolved
Hide resolved
@vikram-raj alignment looks bit off too |
@beaumorley can you take a look into the disabled text inputs with PatternFly? Thanks! |
frontend/packages/pipelines-plugin/src/components/pipelineruns/PipelineRunParametersForm.tsx
Outdated
Show resolved
Hide resolved
frontend/packages/pipelines-plugin/src/components/pipelineruns/PipelineRunParameters.tsx
Outdated
Show resolved
Hide resolved
It looks like the individual disabled fields have a 1 pt stroke at the bottom? If you look at the PF guideline, it is just a plain grey box. https://www.patternfly.org/v4/components/text-input Can we remove the stroke? Also, it you take a look at a disabled on the admin side there is no stroke. Example: FYI @serenamarie125 |
@beaumorley Fixed disable style. |
@invincibleJai Fixed the alignment issue in this PR #11799 |
/retest |
@invincibleJai: GitHub didn't allow me to request PR reviews from the following users: check, and, add, for, once, done, do, e2d, label. Note that only openshift members and repo collaborators can review this PR, and authors cannot review their own PRs. 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. |
/cc @sanketpathak |
/lgtm |
/retest |
@@ -231,6 +232,9 @@ export const pipelineRunDetailsPO = { | |||
}, | |||
status: '.odc-taskrun-details__status', | |||
}, | |||
parameters: { | |||
form: '[data-test="pipelineRun-parameters"]', |
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.
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: hemantsaini-7, invincibleJai, vikram-raj 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 |
@vikram-raj thanks for fixing the disabled pattern. LGTM. |
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.
Propagating docs and px acks from the Epic ODC-4793
/label docs-approved
/label px-approved
/label qe-approved |
/retest |
@vikram-raj: 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. |
Story: https://issues.redhat.com/browse/ODC-6709
Description:
Screenshots:
Tests e2e: