PathMustBeUnique doesn't consider the HTTP Method #1449

Activity

1. darrelmiller commented on Nov 28, 2023

   

   Darrel (darrelmiller)

   on Nov 28, 2023

   Member

   More actions

   Are you creating the GET and DELETE operations under two different path items? If you create both GET and DELETE under the same path Item there should not be any error. Can you show an example of an OpenAPI description that gives you an error.
2. marcusber commented on Nov 29, 2023

   

   Marcus Bernander (marcusber)

   on Nov 29, 2023

   More actions

   Darrel (@darrelmiller) :

   Created a small test to illustrate the problem.

   The controller looked like this:

   using Microsoft.AspNetCore.Mvc;
   
   namespace OpenApi.IntegrationTest;
   [Route("api/v2/someroute/areatype")]
   public class TestController : ControllerBase
   {
       [HttpGet("{index}/{arg}")]
       public ActionResult Get(long index, string arg)
       {
           return Ok("Get");
       }
   
       [HttpPut("{index}/{language}")]
       public ActionResult Put(int index, string language, string text) {
           return Ok("Update");
       }
   }
3. baywet commented on Feb 27, 2025

   

   Vincent Biret (baywet)

   on Feb 27, 2025

   Member

   More actions

   Thank you for the additional information.

   This is actually exactly prevented by the specification because it leads to ambiguous resolution.

   This would need to be addressed at the specification level where the path parameters should be disambiguated considering the type as well.

   Closing as until the specification changes, there nothing that can be done here.
4. Vincent Biret (baywet)

   closed this as not plannedon Feb 27, 2025