Using Fluent Validation with Conventional Controllers #937

4 Answer(s)

• 

  0

  maliming created 3 years ago

  Support Team Fullstack Developer

  hi

  Can you share the full source code to reporduce the problem?

  Save Cancel
• 

  0

  Thiqah.Abp created 3 years ago

  hi

  Can you share the full source code to reporduce the problem?

  I have reproduced the case with just an empty template and a simple application service bellow:

  In Application.Contracts project:

  [DependsOn(typeof(AbpFluentValidationModule)] Added to Module class

  //Dto
  public class SampleInputDto : EntityDto<Guid>
  {
      public string RegistrationNumber { get; set; }
  }
  
  //Validator
  public class SampleInputValidator : AbstractValidator<SampleInputDto>
  {
     public SampleInputValidator()
     {
        RuleFor(input => input.RegistrationNumber)
              .NotEmpty()
              .MaximumLength(25);
     }
  }
  
  //Application service Interface
  public interface ISampleAppService
  {
     Task AddAsync(SampleInputDto input);
  }
  

  In Application project:

  public class SampleAppService : AbpFluentValidationDemoAppService, ISampleAppService
  {
       [Route("add")]
       public Task AddAsync(SampleInputDto input)
       {
           return Task.CompletedTask;
       }
  }
  

  In HttpApi project (Controllers):

  [Route("api/Sample")]
  public class SampleController : AbpFluentValidationDemoController, ISampleAppService
  {
       private readonly ISampleAppService _sampleService;
  
       public SampleController(ISampleAppService sampleService)
       {
           _sampleService = sampleService;
       }
  
      [HttpPost]
      [Route("add")]
      public Task AddAsync(SampleInputDto input)
      {
          return _sampleService.AddAsync(input);
      }
  }
  

  Save Cancel
• 

  0

  maliming created 3 years ago

  Support Team Fullstack Developer

  hi

  The SampleAppService inherited the IValidationEnabled interface, but SampleController not.

  Defines IValidationEnabled to add automatic validation to an arbitrary class. Since all the application services inherently implements it, they are also validated automatically.

  https://docs.abp.io/en/abp/latest/Validation https://docs.abp.io/en/abp/latest/Validation#validation-infrastructure

  Save Cancel
• 

  1

  Thiqah.Abp created 3 years ago

  Still not working! Calling the generated conventional controller does not validae the input. However, after reading the documentation again and again, I figured the issue:

  ABP framework uses the dynamic proxying / interception system to perform the validation. In order to make it working, your method should be virtual or your service should be injected and used over an interface (like IMyService).

  https://docs.abp.io/en/abp/latest/Validation#validation-infrastructure

  Our problem is that the Application Service Method is not virtual, after adding the virtual keyword to the method, it works.

  Save Cancel