http post action not reached in ASP.NET Core 3.1 web API controller-CodePudding

I have this controller

[ApiController]
[Route("api/[controller]")]
public class PlanningController: ControllerBase
{
 public async Task<IActionResult> SaveTest([FromBody] TestData     data)
{      

  return Ok(data);

}

public class TestData
{
 public int Id { get; set; }
 public string Name { get; set; }
}

This in Startup.cs

public void Configure(IApplicationBuilder app, IHostingEnvironment env)
{
      if (env.IsDevelopment())
      {
        app.UseDeveloperExceptionPage();
      }
      else
      {
       app.UseHsts();
      }

      app.UseCors("default");
      app.UseHttpsRedirection();
      app.UseRouting();
      app.UseAuthentication();
      app.UseAuthorization();

      app.UseEndpoints(endpoints =>
      {
        endpoints.MapControllers();
      });

      app.Run(context =>    context.Response.WriteAsync("Planificador API iniciada"));
}

I put a break point in the return but when I post this in postman

nothing happens in my controller the break point is not reached.

I don't understand the response received in postman

In VS 2022 I see this

Microsoft.AspNetCore.Hosting.Diagnostics: Information: Request    
starting HTTP/1.1 POST 
http://localhost:5001/api/planning/saveTest    application/json     34
Microsoft.AspNetCore.Hosting.Diagnostics[1] 
Microsoft.AspNetCore.Hosting.Diagnostics: Information: Request    finished in 8.3968ms 200 
Microsoft.AspNetCore.Hosting.Diagnostics[2]
Request finished in 8.3968ms 200

Any idea, please?

Thanks

CodePudding user response：

Nothing happens in my controller the break point is not reached.I don't understand the response received in postman

Well, because of using [Route("planning")] before your PlanningController it is certainly overriding your application standard routing. So, your controller route has been changed. Thus, you shouldn't manipulate this routing

Note: I would highly recommend you to have a look on our official document for Custom route constraints

CodePudding user response：

Solved...

The problem was tha in my controller I was injected IFileProvider wrong

Unable to resolve service for type 'Microsoft.Extensions.FileProviders.IFileProvider' while attempting to activate my controller