feature: Custom Formatters in ReactiveValidationObject #154
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.
What kind of change does this PR introduce?
Currently, our
INotifyDataErrorInfo
implementation doesn't support custom formatters. The support for custom validation text formatters might be useful in cases when one needs to implement localization in their application via passing resource keys toValidationRule
calls instead of validation messages.What is the current behavior?
Currently, there is no way to customize messages emitted by
INotifyDataErrorInfo
.What is the new behavior?
Now, in order to customize the messages emitted by
INotifyDataErrorInfo
, one needs to either pass an instance of a customIValidationTextFormatter<string>
toReactiveValidationObject
constructor, or to register a defaultIValidationTextFormatter<string>
globally viaLocator.Current.RegisterConstant
, as documented in #153What might this PR break?
Nothing, this change shouldn't be breaking.