SRVKP-11395: Refactor: Inline useTaskRun, useTaskRuns2, and usePipelineRun wrappers into their consumers#1037
Conversation
|
@anwesha-palit-redhat: This pull request references SRVKP-11395 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "5.0.0" version, but no target version was set. DetailsIn 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 openshift-eng/jira-lifecycle-plugin repository. |
|
@anwesha-palit-redhat: This pull request references SRVKP-11395 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "5.0.0" version, but no target version was set. DetailsIn 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 openshift-eng/jira-lifecycle-plugin repository. |
c0aa3bf to
0a68faa
Compare
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: anwesha-palit-redhat 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 |
|
@anwesha-palit-redhat: This pull request references SRVKP-11395 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "5.0.0" version, but no target version was set. DetailsIn 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 openshift-eng/jira-lifecycle-plugin repository. |
0a68faa to
06a86f8
Compare
|
@anwesha-palit-redhat: This pull request references SRVKP-11395 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "5.0.0" version, but no target version was set. DetailsIn 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 openshift-eng/jira-lifecycle-plugin repository. |
Summary
No logical or functional changes are added in this PR
useTaskRuns2,useTaskRun,usePipelineRun) that only delegated touseRuns, inlining their logic at the call sites inTaskRunDetailsPageandPipelineRunDetailsPage.nameandlimitoptions toUseTaskRunsOptionsandusePipelineRunsso consumers can fetch a single resource by name without needing a dedicated wrapper hook.useRunsDetails
useTaskRuns2removeduseRuns<TaskRunKind>.useTaskRunsnow callsuseRunsdirectly.useTaskRunremovedTaskRunDetailsPagenow callsuseTaskRunswith{ name, limit: 1 }and picks[0]. Error-suppression logic in the old wrapper was unused by the consumer.usePipelineRunremovedPipelineRunDetailsPagenow callsusePipelineRunswith{ name, limit: 1 }and picks[0]. Same — error-suppression was unused.useMemoremoved fromuseRunsreturnmcPendingAdmission,mcProxyUnavailable,effectiveLoaded,effectiveErrorwere missing from the dep array).Screen recording
PipelineRun and TaskRun Details Page
PipelineDetailsClusterWorking.mov
PipelineRunRunningWorking.mov
The logs do not show up in this one as the loki setup is not done in this cluster
PipelineRunArchivedWorking.mov
Pipeline Overview Page navigation
OverviewPageNavigation.mov
Pipeline Metrics Page navigation with OSP 1.21.1 and OCP 4.21
PipelineMetricsNavigationOSP1.21.1OCP4.21.mov
Pipeline Metrics Page navigation with latest changes and OCP 4.22
PipelineMetrics_OSP_master_OCP_4.22.mov