Workflow UI improvements, support for workflow v2 schema and new features#567
Merged
bgentry merged 4 commits intoprereleasefrom May 8, 2026
Merged
Workflow UI improvements, support for workflow v2 schema and new features#567bgentry merged 4 commits intoprereleasefrom
bgentry merged 4 commits intoprereleasefrom
Conversation
Update the River Pro module set used by `riverproui` so the backend can consume the newer workflow data exposed for workflow v2 wait, timer, and signal support.
bgentry
force-pushed
the
bg/workflow-v2
branch
2 times, most recently
from
c3482de to
69a6cc9
Compare
Expose workflow v2 task data from the River Pro API, including task wait reasons and the newer backend workflow fields needed by the UI. The handler tests now exercise the serialized workflow detail shape instead of relying on frontend-derived placeholders. The wait-reason mapping uses a direct switch over the River Pro enum so unknown values continue to fall back to the existing `none` state.
Render workflow v2 wait metadata in the diagram and detail views using the final wait terminology instead of the earlier gate model. Tasks now show wait phases, timer and signal evidence, dependency progress, and wait reasons from the backend workflow detail payload. Add the dedicated wait inspector, denser detail layouts, task timeline, and Storybook coverage used to inspect workflow waits across timers, signals, dependencies, and mixed conditions. The diagram tests and factories now cover the wait-aware graph and node states directly.
Only expose workflow routes and navigation when the backend reports that workflow v2 tables are available. Installations without those tables now fall back to the empty-state guidance instead of linking users into views that cannot load workflow detail data. Move the availability check into the River Pro handler response so the UI can make the routing decision from the same feature metadata it already uses for navigation.
Contributor
Author
|
@brandur I don't think you need to do more than a light review on the actual UI parts here, but I'd certainly appreciate a thorough review of everything Go-related 🙏 |
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
2 participants
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.
This moves riverui to be compatible with riverpro's upcoming workflow v2 schema with additional tables. It also adds support for new timer and signal features (collectively: "wait conditions").
It's based on the new
prereleasebranch because it requires workflows v2 given that it links against the riverpro version whose queries depend on that schema. We'll cut this as an RC alongside riverpro v0.24.0-rc.1.It includes a ton of refinements to the workflow diagram and also adds a timeline to the workflow task section.