You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I noticed that for the endpoint /client/getContacts/{sessionId}, the Swagger JSON is generating the following response for status 200:
I have no idea why the swagger.json is being generated incorrectly or if generating the client SDK with NSwag will create another functional endpoint
generated swagger.json
"200": {
"description": "OK"
}
This prevents the correct SDK generation via NSwag.
The solution I found is quite crude (completely ChatGPT), but for now, it works.
I noticed that for the endpoint /client/getContacts/{sessionId}, the Swagger JSON is generating the following response for status 200:
I have no idea why the swagger.json is being generated incorrectly or if generating the client SDK with NSwag will create another functional endpoint
generated swagger.json
This prevents the correct SDK generation via NSwag.
The solution I found is quite crude (completely ChatGPT), but for now, it works.
fix swagger.json
bash command to build sdk
nswag openapi2csclient /input:.\swagger.json /output:WhatsappClient.cs /namespace:{YourNameSpace}.WhatsappClient /classname:WhatsappClient /OperationGenerationMode:SingleClientFromPathSegments
The text was updated successfully, but these errors were encountered: