Bug: Path with parameter incorrectly translated to an OpenAPI spec path

[waldekmastykarz]

If you generate an OpenAPI spec for a request that ends with a parameter, the OpenApiSpecGeneratorPlugin incorrectly adds a trailing slash to the generated path. This leads to a mismatch for subsequent requests and issues in API onboarding scenarios with API Center where the request can't be matched to a previously onboarded request.

Repro

Generate API spec for curl -ix http://127.0.0.1:8000 -X DELETE https://jsonplaceholder.typicode.com/posts/1

Expected

API spec with path /posts/{posts-id}

Actual

API spec with path /posts/{posts-id}/