Fork me on GitHub
#yada
<
2016-07-15
>
jsyrjala06:07:26

Hi, is there any way to attach descriptions to query or path parameters, so that they would appear in swagger-ui?

lmergen09:07:06

aside from increasing the log level, are there any debugging facilities for yada ?

lmergen09:07:46

i'm still trying to debug the swagger-ui issue i'm having with the 500 internal server error, and at the moment i'm just adding debug statements to a local copy of the yada repository

lmergen09:07:27

(and, as I found out, the error/exception being thrown is not at all related to the actual error, which is an internal schema validation issue of swagger itself)

lmergen09:07:20

this happens on my machine even with a non modified clone of the juxt/edge repository, btw, so it probably really has something to do with my environment (perhaps my browser is sending the wrong request headers?)

dominicm11:07:33

@lmergen: Not a real answer, but you might have some luck with tools.trace

lmergen11:07:07

i found the bug

lmergen11:07:08

when the url does not exist, it sets last-modified to nil, which causes this error

lmergen11:07:45

in the case of swagger-ui, this is the location of the jar

lmergen11:07:26

i feel this probably has to do something with my environment (i'm using mingw64 under windows, so perhaps my environment is being detected as being unix, so the url cannot be properly resolved?)

lmergen11:07:25

i think this justifies a bug report

lmergen11:07:10

(an easy fix is to not emit last-modified when the file does not exist, instead of asigning nil to it, but i have a feeling there is a different root cause)

lmergen12:07:22

there we are

jsyrjala12:07:00

Tested it and above works