Introduce new syntax for Transform, deprecate the old version #1613
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.
Marks the current
Transform
syntax as obsolete, and introduces a new transform syntax as part of the call to RuleFor.Old:
New:
There is also a
TransformForEach
method available (equivalent of the oldRuleForEach(expr).Transform(transformer)
)This change is needed as we're moving to generics in the internal API for FluentValidation 10, which means transforming the type will no longer be possible after rules have been created.
The old syntax should be deprecated in the next 9.x release, and removed in 10.0.