You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This PR fixes the outcome logic for OrConstraintResult by correcting the order of condition checks in the Or method. The fix ensures that Success outcomes properly short-circuit the evaluation, returning Success immediately when either operand is successful, which aligns with logical OR semantics.
Key changes:
Corrected the Or method logic to prioritize Success outcomes over Undecided
Enhanced test infrastructure with better equality implementations and value handling
Added comprehensive test coverage for node equality, negation, and mapping behaviors
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This PR fixes the outcome logic for OrConstraintResult by correcting the order of condition checks in the Or method. The fix ensures that Success outcomes properly short-circuit the evaluation, returning Success immediately when either operand is successful, which aligns with logical OR semantics.
Corrected the Or method logic to prioritize Success outcomes over Undecided
Enhanced test infrastructure with better equality implementations and value handling
Added comprehensive test coverage for node equality, negation, and mapping behaviors
Reviewed Changes
Copilot reviewed 14 out of 14 changed files in this pull request and generated 1 comment.
Show a summary per file
File
Description
Source/aweXpect.Core/Core/Nodes/OrNode.cs
Fixed Or method logic and improved GetHashCode implementation
Source/aweXpect.Core/Core/Nodes/AndNode.cs
Enhanced GetHashCode implementation for consistency
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
bugSomething isn't workingcoverageAdditional tests for edge cases or improvement of test coveragestate: releasedThe issue is released
2 participants
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.
This PR fixes the outcome logic for
OrConstraintResultby correcting the order of condition checks in theOrmethod. The fix ensures thatSuccessoutcomes properly short-circuit the evaluation, returningSuccessimmediately when either operand is successful, which aligns with logical OR semantics.Key changes:
Ormethod logic to prioritizeSuccessoutcomes overUndecided