API Gateway generated sdk overriding subsequent path params

I have a resource a/{id}/c with a GET method on my API Gateway.

The generated SDK for this method/resource ends up calling GET on resource a/{id} instead of a/{id}/c. So the /c part of the path is being overriden, i am passing params {id: id} only since /c is a contant and I assume should be left untouched. This is only happening on GET requests, similar POST requests work as expected by only replacing {id} in the path.

How can i ensure that /c is not being skipped on the actual request?