PipelineBehaviorOrderRule
Defined in: packages/pipeline/src/interfaces/pipeline-behavior-contract.interface.ts:71
Static ordering constraints relative to other pipeline behaviors.
These are relative-position constraints, not dependency declarations. A
target that is absent from the handler’s effective chain produces no
diagnostic, because there is no position to violate. after: [CaslBehavior]
therefore means “must not run before CaslBehavior when it is present”, not
“CaslBehavior must be present”.
To require a peer, check PipelineBehaviorValidationContext.effectiveBehaviorTypes in IPipelineBehaviorContract.validate and return a diagnostic when it is missing. Ordering alone cannot express that.
Properties
Section titled “Properties”after?
Section titled “after?”
optionalafter?: (string|Constructor<IPipelineBehavior<unknown,unknown>>)[]
Defined in: packages/pipeline/src/interfaces/pipeline-behavior-contract.interface.ts:75
This behavior must execute after the specified behaviors, when present.
before?
Section titled “before?”
optionalbefore?: (string|Constructor<IPipelineBehavior<unknown,unknown>>)[]
Defined in: packages/pipeline/src/interfaces/pipeline-behavior-contract.interface.ts:73
This behavior must execute before the specified behaviors, when present.