Filter by title
No results found!
IObjectValidator is implemented by theObjectValidator by default.ObjectValidator is extensible; you can implementIObjectValidationContributor interface to contribute a custom logic. Example:
public class MyObjectValidationContributor : IObjectValidationContributor, ITransientDependency{ public Task AddErrorsAsync(ObjectValidationContext context) { //Get the validating object var obj = context.ValidatingObject; //Add the validation errors if available context.Errors.Add(...); return Task.CompletedTask; }}- Remember to register your class to theDI (implementing
ITransientDependencydoes it just like in this example) - ABP will automatically discover your class and use on any type of object validation (including automatic method call validation).
IMethodInvocationValidator
IMethodInvocationValidator is used to validate a method call. It internally uses theIObjectValidator to validate objects passes to the method call. You normally don't need to this service since it is automatically used by the framework, but you may want to reuse or replace it on your application in rare cases.
FluentValidation Integration
Volo.Abp.FluentValidation package integrates the FluentValidation library to the validation system (by implementing theIObjectValidationContributor). See theFluentValidation Integration document for more.
