Clarification Needed on Path Template Normalization in Find Function for Swagger Document Generation

[dwertent]

Could you clarify the rationale behind normalizing path templates in the Find function? Specifically, in cases where different paths use similar templates (like {iid} and {did}), is normalization intended to handle such scenarios? We're evaluating whether this behavior is essential for Swagger document generation, and understanding its original purpose would help us decide if and when normalization makes sense.

Here is an example of the expected document:

  /identities/{iid}:
    get:
      description: Gets an identity by its ID
      operationId: getIdentityByID
      parameters:
      - description: The identity ID 
        in: path
        name: iid
        required: true
        schema:
          example: id
          type: string
       ...
  /identities/{did}:
    get:
      description: Gets an identity by its DID
      operationId: getIdentityByDID
      parameters:
      - description: The identity DID 
        in: path
        name: did
        required: true
        schema:
          example: did
          type: string
        ...

[dwertent]

I found this mentioned in the specifications, if this is the case, I don't understand how the docs generation succeeds:

[LasneF]

Given the provided specification snippet and, given the OAS 2.0 and 3.0 definition this case is qualified as invalid api

notice the source of truth for the specification is no more [swagger.io]
(https://swagger.io/specification/#:~:text=The%20following%20paths%20are%20considered%20identical%20and%20invalid%3A) that belong to the trademark Smartbear , but rather than openapis

notice if you leverage this website that allows basic validation
https://editor.swagger.io/ you will get those 2 clear errors

Semantic error at paths./stores/{store_id}
Equivalent paths are not allowed.

[handrews]

@dwertent questions regarding the Swagger suite of tools should be directed to SmartBear, the provider of those tools. AFAICT, normalization is not mentioned in the specification itself, so I'm not sure what they're talking about here.