Swagger: “equivalent path already exists” despite different parameters

by

That’s because the two paths can be identical. I understand that the parameters may uniquely identify them, but OpenAPI 2.0 (Swagger 2.0), 3.0 and 3.1 do not support full URI templates, and the path portion alone is inspected for uniqueness. So these:

/{foo}
/{bar}

are identical, even if foo must be a string, and bar must be a number. Please add your $0.02 on the OpenAPI Specification Repo as we’re working on better path support right now.

More Related Contents:

  1. How to document dynamic query parameter names in OpenAPI (Swagger)?
  2. How to write OpenAPI 3 (Swagger) specification for property name in `map` object?
  3. Swagger: How to have a property reference a model in OpenAPI 2.0 (i.e. nest the models)?
  4. How to specify if a field is optional or required in OpenAPI/Swagger?
  5. How to return an array of objects in SwaggerHub?
  6. How to define a mixed-type array (with different element types) in OpenAPI 2.0?
  7. How can I represent ‘Authorization: Bearer ‘ in a Swagger Spec (swagger.json)
  8. How to define a property that can be string or null in OpenAPI (Swagger)?
  9. Swagger schema properties ignored when using $ref – why?
  10. How to define mutually exclusive query parameters in Swagger (OpenAPI)?
  11. Swagger 2.0: Multiple Path objects with different paths but same request and response
  12. Swagger/OpenAPI – use $ref to pass a reusable defined parameter
  13. How to convert OpenAPI 2.0 to OpenAPI 3.0? [closed]
  14. Swagger complex response model with dynamic key value hash maps
  15. Swagger: wildcard path parameters
  16. How to define an optional parameter in path using swagger
  17. Re-using model with different required properties
  18. How not to copy-paste 3 generic error responses in almost all paths?
  19. How to define global parameters in OpenAPI?
  20. Schema object without a type attribute in Swagger 2.0
  21. Swagger: take one or more values from enum
  22. Swagger Inheritance and Composition
  23. Swagger/OpenAPI mock server
  24. Swagger: map of
  25. Use object type query param in swagger documentation
  26. How do I include subclasses in Swagger API documentation/ OpenAPI specification using Swashbuckle?
  27. How to add multiple example values for an array in OpenAPI/Swagger?
  28. How to format Swagger 2.0 text descriptions?
  29. Combining defintions in Swagger docs
  30. Why `additionalProperties` is the way to represent Dictionary/Map in Swagger/OpenAPI 2.0

Leave a Comment