Repository navigation
feat(ui): show a flow's run as its steps - #444
Merged
Merged
Conversation
For a flow the Runs step draws one box per step from the run's stages, joined by what each step waits for, with a list of the steps, their status and any error. It replaces the model-shaped rows, which do not apply. Also for a flow: the headline says flow, the maximum run time field and the publish controls are not shown, publishers are not requested, and the run records are read again after submit and when the run changes state. The records table says so when it is empty, where it said it was loading.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
C1(c) of the plan in #441 (flows in the MINT web app).
For a flow the Runs step draws one box per step from the run's stages, joined by what each step waits for, with a list of the steps, their status, task id and any error. It replaces the model-shaped rows (prepare inputs, run model, pass inputs to model), which do not apply to a flow.
Also for a flow:
A model that is not a flow renders as before.
Checked in a browser with a local build against the dev services, on a completed Dictionary flow run: four steps drawn with their links, the records table loads.
Tests: 1321 passing, type check clean.