Class InitializationPipelineCriticalityRule
The single encoding of the initialization pipeline's criticality rule: a
Critical failure halts the boot (skipping every remaining step); any
other failure is logged and boot continues, consuming the step's weight like a success. Both
InitializationPipelineService.RunAsync (the real executor) and the editor's dry-run simulator
(SerenityInitPipelineSimulatorWindow) consume this so the "what happens if this task fails?"
preview can never drift from the runtime behavior.
Inheritance
InitializationPipelineCriticalityRule
Assembly: Serenity.InitializationPipeline.Application.dll
Syntax
public static class InitializationPipelineCriticalityRule
Methods
HaltsOnFailure(TaskCriticality)
True when a failure of a step with this criticality halts the pipeline (skips the rest).
Declaration
public static bool HaltsOnFailure(TaskCriticality criticality)
Parameters
Returns
Simulate(IReadOnlyList<InitializationPipelineStep>, IReadOnlyList<bool>)
Simulates running plan given which steps are injected to fail
(willFail, same length/order as plan), applying the same
weight-accumulation and halt-on-critical-failure rule as InitializationPipelineService.RunAsync.
Does not execute anything — a pure "what would happen" projection.
Declaration
public static InitializationPipelineCriticalityRule.SimulationResult Simulate(IReadOnlyList<InitializationPipelineStep> plan, IReadOnlyList<bool> willFail)
Parameters
Returns