-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Fixes cloning of recurring runs #1712
Conversation
Simplifies NewRun a little Creates NewRunParameters component
/retest |
@@ -170,8 +171,8 @@ class RecurringRunDetails extends Page<{}, RecurringRunConfigState> { | |||
const pageTitle = run ? run.name! : runId; | |||
|
|||
const toolbarActions = [...this.props.toolbarProps.actions]; | |||
toolbarActions[1].disabled = !!run.enabled; | |||
toolbarActions[2].disabled = !run.enabled; | |||
toolbarActions[2].disabled = !!run.enabled; |
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 can probably improve upon the practice of accessing toolbar items by index.
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 will work on a follow-up PR for this
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.
Follow-up: #1812
/lgtm |
/retest |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: rileyjbauer 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 |
Fixes #1266
Simplifies NewRun a little by separating out NewRunParameters into its own component.
There were a number of issues with the way recurring runs were handled in the frontend and backend that were addressed in this PR and the others referenced in #1266.
With this PR, users can no longer swap between one-off and recurring when cloning a run. Recurring runs and single runs are ostensibly similar but there are nuances to the way they are handled in the backend that makes treating them as interchangeable problematic.
Similarly, users can no longer switch Pipelines after reaching NewRun via cloning. This extra flexibility isn't worth the complexity it adds.
This PR also adds a
clone
button to the details page for a recurring run.Keeping track of parameters within the Pipeline object in NewRun was causing problems because in that component, Pipeline can be an API Pipeline object or something else such as a manifest from a run created from a notebook. To address this, parameters are now kept separately in their own variable in NewRun's state.
This change is