-
Notifications
You must be signed in to change notification settings - Fork 584
Hello World Endpoint throwing Exception #348
Comments
I did add some logging in swagger-validator when the validation fails: `
Thanks |
It looks like the template is actually wrong and some new validation logic in a library picked it up. Quick fix, change your swagger.yaml to have this:
Instead of this:
|
That worked! I don't know the etiquette around this stuff. Should I close it? Fork and submit pull request. I'm kind of new to the github community. Thanks |
If you find something wrong with the doc and want to fix it, then yeah, submitting a PR would be greatly appreciated. |
@theganyo Thank you! This worked perfectly. |
@theganyo The pattern, of describing a simple string response as a message object is used several places in several templates. Are we sure this new validation logic is valid and the templates should be changed (via a PR) as you described above? |
Its explained and resolved here . But not present in the code set swagger-api#348 . Platform: Node-Express
updated the templates |
Thanks! |
I followed the instructions on the quick start page, selecting express as the framework.
When I hit the endpoint with curl, I get a truncated json response message:
{"message":"Res
The error below shows up on the console.
Thanks!
The text was updated successfully, but these errors were encountered: