-
Notifications
You must be signed in to change notification settings - Fork 130
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
Getting "null" in response definition #66
Comments
Can you double check if your |
The indent looks like what I would expect. The formatting (leading spaces) seems to get lost when you cut and paste here? |
Ack, found the problem, there was a tab embedded in the indenting. Other portions of the same routes file have resulted in exceptions being thrown when tabs were embedded, that would likely be the better option here also? |
we will add swagger validation in the future |
…re-4.20.4 Update specs2-core, specs2-mock to 4.20.4
First, great project, many thanks for your work!
In my routes I have comments as follows:
(#'s removed to keep formatting sort of normal)
In the resultant swagger.json I get:
"/":{ "get":{ "tags":[ "routes" ], "summary":"default module", "description":"get the default module description", "responses":null, "200":{ "description":"Modules definition", "schema":{ "$ref":"#/definitions/models.Protocol.ModuleDef" } },....
Note the "null" instead of the JSON object start for the response. The object that is being referenced is included in the definitions so it's not a case of a broken reference.
I'm running Play 2.5 but get the same result with 2.4.6. Build is using 0.2.0 not the 0.2.1 Play 2.5 specific version since that is currently throwing JSLookup errors when I try to use it instead.
The text was updated successfully, but these errors were encountered: