Generated client is not working when there are more than one API's with the colon in the API path

[soodpr]

There seems to be a bug if the API spec contains more than one API's with colon in the API Path, it always return the response of 1st API.
I have put an example in this repo here: https://github.com/soodpr/oapi-codegen-bug

If we run both server and client code in the above example, the expected output from the client main program is that it first calls the /pets:validate and then /pets:generate API but in reality, its always end up calling /pets:validate API twice.

Let me know if you require any further details on this.

[cosban]

soodpr's example is based on echo, but this issue is also present with gin. It seems that the code generator needs to update its SwaggerUriToGinUri and SwaggerUriToEchoUri methods to include escaping the literal colon characters.

I believe such an update would not take very long to implement and I would be willing to submit an PR for it if doing so helps speed up getting the fix in.

labstack/echo#2046
gin-gonic/gin#1432

[cosban]

In the meantime, you may be able to work around the issue by manually escaping these paths yourself in the spec.

i.e. /pets\\:generate

The only problem is that the escape characters will show up in the spec, which means it will not be accurate.

[holyfuchs]

the issue is also present in fiber.
Escaping the paths in the same way fixes it as well.