[SP-8499] Introduce always step#40
Merged
Merged
Conversation
Closed
petergebala
approved these changes
Apr 16, 2026
kikorb
approved these changes
Apr 16, 2026
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.
Introduces a new
alwaysDSL instruction that runs a step unconditionally at the end of the operation pipeline — regardless of whether prior steps succeeded, failed, or halted early viafinish!orfinish_ifDSL.How it works
alwayssteps are declared after all regular instructions and execute even when the normal break condition (failure or early finish) would have stopped execution. Inside analwaysstep,result.success?andresult.failure?reflect the final state of the operation, allowing conditional logic based on outcome.Placement rules enforced at class load time
alwayssteps must appear after all other instructions at the top level of the operation.alwaysis declared, only furtheralwayssteps may follow — any other instruction (step,operation,transaction,within, etc.) raises anArgumentErrorat class load time.alwayscannot be used inside blocks (transaction do,within do,success do,validate do). Doing so raises anArgumentErrorat class load time.