My less than ideal work around for now has been to move all my collection
schema definitions into the same directory as my item schema definitions.
This seems to prevent the reference resolver from getting the paths mixed
up.
On Thursday, July 27, 2017 at 10:17:53 AM UTC-5, Austin wrote:
>
>
Hello,
I've ran into a kind of funky problem where I have two operation objects
with similar but not identical schemas. The get operation has a schema
reference that points to a json file containing a standardized mason
wrapper with an items collection in it. This items collection is a list
We gave been using sane v 2.0 swagger doc for a year, but this morning I
tried to verify it, because one of the js tools all of sudden told me it's
not valid (apparently it is powered by the same library). What do you know
the editor gave me Hide
Parser error missed comma between flow
Hi
My maven build show this warning
[WARNING] The following plugins are not marked @threadSafe in adm-agent-core:
[WARNING] io.swagger:swagger-codegen-maven-plugin:2.2.2
[WARNING] org.codehaus.mojo:flatten-maven-plugin:1.0.0
[WARNING] Enable debug to see more precisely which goals are not
