Improve workflow API ergonomics in Rust API

Specifically want this for the rust api.

Right now workflows are in two states: registered (immutable) and unregistered (mutable).

The distinction itself is hidden in the type system making it very easy for a user to mistake an API meant for unregistered workflows for one they can use on a registered workflow.

Adding a WorkflowBuilder or something that acts as a mutable workflow would allow us to use the type system to enforce correct behavior.

This is probably best completed with the PR above, further work could be done to make a proper workflow builder api (something like Workflow::builder().with_activity blah blah blah) but the bulk of the issue is primarily around the the activity configuration in practice.

#7254 now also adds a WorkflowBuilder type and moves all of Workflows methods over to it. You end up with something like:

Workflow::cloned("core.module.metaAnalysis")
    .ok_or(())?
    .activity_before(&activity, "core.module.finishUpdate")?
    .register()?;

Navigation Menu

Repository navigation

Improve workflow API ergonomics in Rust API #6014

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Improve workflow API ergonomics in Rust API #6014

Description

Activity

emesare commented on Aug 11, 2025

bdash commented on Aug 12, 2025

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions