-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Does not generate proper client if two in:path parameters #1124
Comments
any updates on this? |
Very strange, in general multiple path parameters should be supported... |
@RicoSuter Any update on this? It is still not working. If multiple path parameters are explicitly defined, it works as expected. The problem is if multiple path parameters are referencing shared global parameter definitions. In that case, only the first path parameter is generated. If multiple referenced parameters are provided in the operation itself, it works correctly. This works: '/workspaces/{workspaceId}/users/{userId}': --- This does not work '/workspaces/{workspaceId}/users/{userId}': parameters: |
Confirmed, for path with more parameters in URI and $ref in parameter, generated code is bad, cannot be compiled. |
Have the following spec with method with 2 in path parameters:
And the following code is generated:
Generated with:
nswag swagger2tsclient /ClassName:Client /Template:Fetch /PromiseType:Promise /DateTimeType:Date /GenerateClientInterfaces:true /GenerateConstructorInterface:true /GenerateDefaultValues:true /Output:src/client/src/client.ts /TypeStyle:Interface /TypeScriptVersion:2.5 /WrapDtoExceptions:false
The text was updated successfully, but these errors were encountered: