Skip to content

Make Actual parameter position consistent across the new assertions - #2939

Merged
nohwnd merged 1 commit into
mainfrom
fix-2933-actual-parameter-position
Jul 31, 2026
Merged

Make Actual parameter position consistent across the new assertions#2939
nohwnd merged 1 commit into
mainfrom
fix-2933-actual-parameter-position

Conversation

@nohwnd

@nohwnd nohwnd commented Jul 31, 2026

Copy link
Copy Markdown
Member

Fix #2933

The Actual parameter was bound inconsistently across the new assertions. Aligned them all to the same convention: Actual always binds from the pipeline, and takes Position = 0 on single-subject assertions or Position = 1 when a positional Expected/comparand already sits at Position = 0.

🤖

@nohwnd nohwnd added this to the 6.1.0 milestone Jul 31, 2026
@nohwnd
nohwnd merged commit 81d06bd into main Jul 31, 2026
13 checks passed
@nohwnd
nohwnd deleted the fix-2933-actual-parameter-position branch July 31, 2026 18:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Actual parameter position is inconsistent across the new assertions

1 participant