Equivalent paths are not allowed even thogh the path + verb combination is different

Paste this spec in https://editor.swagger.io:

info:
  title: Server
  version: 1.0.0

host: 'localhost:8000'
basePath: /
produces:
  - application/json

schemes:
  - http

swagger: '2.0'
paths:
  
  '/path/{paramName}':
    get:
      summary: Get paramName
      parameters:
        - name: paramName
          in: path
          required: true
          type: string
      responses:
        '200':
          description: Success
  '/path/{someOtherParamNameButTheVerbIsPut}':
    put:
      summary: Update paramName
      parameters:
        - name: someOtherParamNameButTheVerbIsPut
          in: path
          required: true
          type: string
      responses:
        '200':
          description: Success

Though path+verb combinations are different, it throws error. This is not expected at all!

[nickdnk]

I have this problem as well. Consider this:

I want to add multiple entries all under a specific date:

POST /something/{date}

Each entry gets and ID, which means I can delete or update individual entries like this:

DELETE /something/{id} PATCH /something/{id}

{id} needs to be validated as an integer, {date} as a date string, and I cannot just put them under the same path, because then the variable needs to be named something like {dateOrId}, which is super ugly and misleading (but works!).

Given that the methods don’t overlap because of different verbs, there’s no way this can ever cause a conflict, and it works fine in the real world as well.

Please reconsider this limitation in the future.

[hkosova]

TL;DR: This is a limitation of the OpenAPI Specification and not a Swagger Editor issue.

The error means that these paths

/path/{paramName}
/path/{someOtherParamNameButTheVerbIsPut}

are considered identical and therefore invalid. They are identical because there’s no way to tell if /path/foo corresponds to /path/{paramName} or /path/{someOtherParamName}. The parameter name alone does not make the path unique.

What you can do is define a single path /path/{paramName} with 2 operations get and put:

paths:
  /path/{paramName}:
    get:
      ...
    put:
      ...

This limitation has been previously discussed in the OpenAPI Specification repository here: https://github.com/OAI/OpenAPI-Specification/issues/576 https://github.com/OAI/OpenAPI-Specification/issues/788

If you want to change the path matching behavior, file an enhancement request with OpenAPI Specification:
https://github.com/OAI/OpenAPI-Specification/issues