Add support for condition in the specification builder methods. #192
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.
Closes #143. This should be merged after PR #191.
All specification builder methods got an overload that accepts
bool conditionparameter. If this condition is false, the given expression/value is discarded and is not added to the specification. I decided not to implement it as an optional parameter, since that might be a breaking change for someone. TheSelectandPostProcessingActionmethods are an exception, and those methods won't have an overload with this parameter. Once the specification is defined with generic parameters<T, TResult>, then it must contain a selector.Sample Usage:
Since the
IncludeandOrdermethods offer multi-level chaining, if the parent method has false condition, the whole chain afterward is discarded.