Makoto

This was introduced by implementing issue #60. To fix this issue, in Swagger.js, add the following method and edit "SwaggerOperation.protorype.urlify". ``` SwaggerOperation.prototype.pathWithoutQuery = function () { if (!this.path.contains("?")) { return...

Realized that #60 should've been implemented in Swagger-UI layer since it is not a problem with models but is a presentation change. Will ask Swagger-UI project to see how difficult...

I started a discussion with Swagger UI team but they closed the issue and claimed that it is a spec issue. Hmm. https://github.com/wordnik/swagger-ui/issues/506

Apologies for the very late reply. If a method does require authorization, you should see a browser popup asking for your credentials. Swagger-UI project has more information on how to...

I was just thinking it would be nice to be able to remove the "optional" text in data type description of a parameter within a contract. But I guess "optional"...

Unfortunately no, but it is a good idea!

I was thinking it would be nice to be able to use it on a parameter, not just on methods. Anyway maybe this is not really a bug like you...

Another idea to have some sort of a special syntax/logic to split a string into ordered lists.

Back to the System.Guid example, Swaggeratr shouldn't force all System.Guild type to be shown as string(36), as it could be formatted in different ways. Thus adding "UnderlyingType" property approach. http://stackoverflow.com/questions/968175/what-is-the-string-length-of-a-guid