Not generate Path Params if parameters are defined in path dictionary about swaggen HOT 4 CLOSED

Hi @dangthaison91
I'm not sure what you mean? Path parameters are replaced within the actual request when the url request is created https://github.com/yonaskolb/SwagGen/blob/master/Templates/Swift/request.swift#L73

In terms of the struct vs classes, which classes do you mean? If you're talking about the classes in the SwaggerSpec, it's because references, names and other properties are resolved in a spec in a second pass. This would be possible with structs, but it was easier to edit them with classes at the time without accidentally leaving a mutated struct behind.

from swaggen.

Here's an example of the path being replaced in an actual generated operation https://github.com/yonaskolb/SwagGen/blob/master/Specs/petstore/generated/Swift/Sources/API/Requests/Pets/ShowPetById.swift#L41

from swaggen.

Have you tried my YAML sample above @yonaskolb ? I tried with your original template but it didn't generate path parameters. Please notice that in my example, path parameters are put after path value, not in method dictionary.

In OTW, if you use allParams or pathParams, you won't get parameters if they are defined like above example.

from swaggen.

Resolved by #29

from swaggen.