v1.38.1 (Current) ✅
REslava.Result.Flowchain walker bug fix —IInvocationOperation.Instancetraversal stopped after the first node for static roots (Result<T>.Ok(...)) and async extension methods. Fixed with syntax-walk + per-nodesemanticModel.GetOperation()— all pipeline steps reliably captured regardless of calling convention.REslava.Result.Flow— REF002 analyzer + Code Action — native companion package now emits REF002 on every[ResultFlow]method with a detectable chain. Code action inserts a full-fidelity diagram (type travel + typed error edges) as a```mermaidfence comment — rendering inline in VS Code, GitHub, Rider.REslava.ResultFlow—mermaidfence format — "Insert diagram as comment" code action now wraps diagrams in```mermaid … ```fence (was plain/* ... */). Renders inline in any Markdown-aware IDE.samples/result-flow— new standalone sample: REslava.Result.Flow with type travel + typed error edges; 5 pipelines, all node kinds, async.samples/resultflow-fluentresults— new standalone sample: REslava.ResultFlow + FluentResults; 3 pipelines, zero REslava.Result dependency, type travel.- 3 regression tests for chain walk completeness (Ensure×3, Ok-root, 4-step mixed chain)
- 142 features across 13 categories
-
3,900 tests