title: Swagger same path specified twice
body: <p>Is it possible to have same path appear more than once in one API spec which is being rendered by Swagger-UI? </p>
  
  <p>Should I create separate api specs and load two instances of Swagger-UI? What is the best way to handle this?</p>
  
  <p>For ex. I have endpoint called /oauth/token which I want to document with one set of parameters for OAuth Authorization Code flow and the same endpoint /oauth/token documents for client_credentials flow with different set of parameters.</p>
  
  <pre><code>/oauth/token:
      post:
        summary: token endpoint for authorization_code flow
        parameters:
          - name: code
            type: string
            description: Required for Authorization Code Flow
            in: formData
            required: true
          - name: grant_type
            type: string
            description: Grant Type should be specified as authorization_code
            in: formData
            required: true
            default: authorization_code
            enum:
            - authorization_code
            - client_credentials
          - name: client_id
            type: string
            description: Consumer Key
            in: formData
            required: true
          - name: client_secret
            type: string
            description: Consumer Secret
            in: formData
            required: true
          - name: endOtherSessions
            in: formData
            type: boolean
            required: false
            default: false
            description: Optional parameter. Default is false - do not allow concurrent login. Send true to end any other user sessions.
        tags:
          - OAuth2 Authorization Code
  </code></pre>
  
  <p>Same endpoint for client_credentials flow </p>
  
  <pre><code>/oauth/token2:
       post:
         summary: token for client credentials
         parameters:
           - name: grant_type
             type: string
             description: Grant Type should be specified as client_credentials
             in: formData
             required: true
             default: client_credentials
             enum:
            - authorization_code
            - client_credentials
           - name: client_id
             type: string
             description: Consumer Key
             in: formData
             required: true
           - name: client_secret
             type: string
             description: Consumer Secret
             in: formData
             required: true
         tags:
           - OAuth2 Client Credentials
  </code></pre>