Follow Swagger 1.2 specs more precisely

[jeromegn]

Awesome library. I took the liberty of forking it a little bit to follow the new Swagger specs correctly.

---

Resource paths should not include the documentation mount_path.

apis. This is an array of apis available to the caller, and contain the relative path to the API declaration. If no apis are available, an empty array should be returned.

From here: https://github.com/wordnik/swagger-core/wiki/Resource-Listing

---

Operations with the same path, but different HTTP methods should be listed as one api in the apis property.

All HTTP operations for a particular path should be grouped in a single api object. There should be no duplicate HTTP methods for a single path.

From here: https://github.com/wordnik/swagger-core/wiki/API-Declaration

[tim-vandecasteele]

Great, merged

[tim-vandecasteele]

Should've done this before, but did you check the change with the relative path with swagger-ui?

It looks like swagger-ui is actually using the basePath as relative path, which causes it to break at my end. (I checked in a small rack testapp in /test in master).

[jeromegn]

It seems like the example UI here: http://swagger.wordnik.com/ works fine with the same specs.

• Resources list: http://petstore.swagger.wordnik.com/api/api-docs
• (/pet) API Definition: http://petstore.swagger.wordnik.com/api/api-docs/pet

We follow both correctly I believe. Are you using an old UI? Or did they modify their UI?