Merged
Conversation
### Added
- **`Railway.Create()` — two-phase builder factory** that enforces a clear separation between the
guard/validation phase and the step execution phase at the type-system level
- `Railway.Create(factory, selector, guards, steps)` — with guards
- `Railway.Create(factory, selector, steps)` — without guards (convenience overload)
- Parameterless variants (`Func<TPayload>` factory) for railways with no request input
- New `RailwayGuardBuilder<...>` — only exposes `Guard()` and `Validate()`
- New `RailwayStepsBuilder<...>` — only exposes `Do()`, `DoIf()`, `DoAll()`, `Group()`,
`WithContext()`, `Detach()`, `Parallel()`, `ParallelDetached()`, `Finally()`, and `Build()`
### Fixed
- **Registration-order bug**: `Group()`, `WithContext()`, `Detach()`, `Parallel()`, and
`ParallelDetached()` steps now execute in the exact order they were registered, interleaved
correctly with `Do()` steps. Previously all `Do()` steps ran before all feature steps
regardless of registration order.
### Deprecated
- `RailwayBuilder<TRequest, TPayload, TSuccess, TError>` — use `Railway.Create()` instead
- `RailwayBuilderFactory` — use `Railway.Create()` instead
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.
Added
Railway.Create()— two-phase builder factory that enforces a clear separation between the guard/validation phase and the step execution phase at the type-system levelRailway.Create(factory, selector, guards, steps)— with guardsRailway.Create(factory, selector, steps)— without guards (convenience overload)Func<TPayload>factory) for railways with no request inputRailwayGuardBuilder<...>— only exposesGuard()andValidate()RailwayStepsBuilder<...>— only exposesDo(),DoIf(),DoAll(),Group(),WithContext(),Detach(),Parallel(),ParallelDetached(),Finally(), andBuild()Fixed
Group(),WithContext(),Detach(),Parallel(), andParallelDetached()steps now execute in the exact order they were registered, interleaved correctly withDo()steps. Previously allDo()steps ran before all feature steps regardless of registration order.Deprecated
RailwayBuilder<TRequest, TPayload, TSuccess, TError>— useRailway.Create()insteadRailwayBuilderFactory— useRailway.Create()instead