Bug Report Checklist
Description
When we generate with --additional-properties=responseAs=AsyncAwait, I noticed that the .md files generated with it aren't using async await, and instead still referencing completion blocks as examples. This is super minor, but it would be nice to have the docs match the output of the swift file.
Using
openapi-generator version 7.24.0
I think this has always been the case. I'm looking even at the sample code generated in the code base and the docs:
https://github.com/OpenAPITools/openapi-generator/blob/master/samples/client/petstore/swift5/asyncAwaitLibrary/docs/PetAPI.md?plain=1
Generation Details
Swift 6 and Swift 5 both show this
Steps to reproduce
Run the openapi-generator with --additional-properties=responseAs=AsyncAwait and observe that the .md files don't change
Related issues/PRs
Suggest a fix
the .md files should generate sample code that matches the flag set by the user for responseAs
Bug Report Checklist
Description
When we generate with
--additional-properties=responseAs=AsyncAwait, I noticed that the .md files generated with it aren't using async await, and instead still referencing completion blocks as examples. This is super minor, but it would be nice to have the docs match the output of the swift file.Using
openapi-generator version 7.24.0
I think this has always been the case. I'm looking even at the sample code generated in the code base and the docs:
https://github.com/OpenAPITools/openapi-generator/blob/master/samples/client/petstore/swift5/asyncAwaitLibrary/docs/PetAPI.md?plain=1
Generation Details
Swift 6 and Swift 5 both show this
Steps to reproduce
Run the openapi-generator with
--additional-properties=responseAs=AsyncAwaitand observe that the .md files don't changeRelated issues/PRs
Suggest a fix
the .md files should generate sample code that matches the flag set by the user for
responseAs