Question 1

How to handle asynchronous state transitions in Stateless?

Accepted Answer

Use the FireAsync() method to fire triggers and configure entry/exit actions with OnEntryAsync() or OnExitAsync(). Ensure all async handlers are registered via the *Async() configuration methods, as outlined in the async triggers section.

Question 2

Stateless vs Windows Workflow Foundation: which is better for .NET workflows?

Accepted Answer

Stateless is lightweight and code-first, ideal for embeddable state machines without overhead. WF is better for complex, long-running workflows with built-in persistence, designer tools, and orchestration features.

Question 3

How to export a state machine diagram for documentation?

Accepted Answer

Call UmlDotGraph.Format() for DOT graphs or MermaidGraph.Format() for Mermaid diagrams, passing the state machine info. These can be rendered with tools like Graphviz or directly in GitHub Markdown for visualization.

Question 4

Can Stateless be used with Blazor or ASP.NET Core for UI state?

Accepted Answer

Yes, its external state storage allows binding to Blazor components or ASP.NET Core services. Use the constructor delegates to sync state with UI properties, but handle lifecycle and concurrency carefully.

Question 5

What are guard clauses and how do they work?

Accepted Answer

Guard clauses are conditional functions attached to transitions using PermitIf() or PermitIfAsync(). They control state changes based on logic, but must be mutually exclusive within a state to avoid conflicts.

Question 6

How to persist state externally with Entity Framework?

Accepted Answer

Pass lambdas in the StateMachine constructor that read from and write to EF-mapped properties, as shown in the external storage example. This decouples persistence but requires manual transaction handling.

Stateless

What is Stateless?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions