Only Use IOrderedCondition in Fluent Syntax Implementation

[alexanderlinne]

The ConditionManager now expects every condition to be an IOrderedCondition. This simplifies the implementation in the condition manager since it no longer has to differentiate between condition types.

To keep the current interface and fluent syntax implementation, ICondition now has a new extension method AsOrderedCondition, which wraps the given ICondition in a class that orders the results in the same order as the input elements. If the given ICondition already is an IOrderedCondition it is returned directly.

[codecov-commenter]

Codecov Report

❌ Patch coverage is 76.58228% with 37 lines in your changes missing coverage. Please review.
✅ Project coverage is 73.69%. Comparing base (7e03a8a) to head (163656f).

Files with missing lines	Patch %	Lines
.../MethodMembers/MethodMemberConditionsDefinition.cs	57.14%	24 Missing ⚠️
.../Syntax/Elements/Types/TypeConditionsDefinition.cs	80.00%	9 Missing ⚠️
...chUnitNET/Fluent/Conditions/ConditionExtensions.cs	85.71%	2 Missing and 2 partials ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #441      +/-   ##
==========================================
- Coverage   73.78%   73.69%   -0.10%     
==========================================
  Files         259      260       +1     
  Lines       16385    16463      +78     
  Branches     1336     1337       +1     
==========================================
+ Hits        12090    12132      +42     
- Misses       3878     3912      +34     
- Partials      417      419       +2     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.