Yonas Kolb

The readme is indeed out of date. The `RequestAuthorizer` has been replaced with `RequestBehaviour.validate` which allows you to do the same thing - asynchronously modify the request or fail

Having a 200 range response in swagger is optional. You can edit the template if your api always has a success response though. This also lets you build a convenience...

Thinking about this, an improvement could be to see if all the possible responses in a spec have 200 range responses and then making this non optional in the protocol

Sorry, I actually missunderstood, the reason this is optional is that the endpoint may fail so the success property is optional. The initial result is if the endpoint returned anything...

Hi @mitrenegade. File references are currently unsupported in SwagGen. There are no immediate plans to support them, but PR's are welcome

`#ref` wouldn’t be parsed at all so you’d just end up with an empty Pet Schema definition

Hi @stherold. This would be a great addition to the list of fixtures we have in https://github.com/yonaskolb/SwagGen/tree/master/Specs Would you like to open a PR that adds that and run `build_specs.sh`,...

Happy to accept an easy PR for this

Renaming models from https://github.com/yonaskolb/SwagGen/issues/90 can resolve this

It sounds like you need to be using enum instead of oneOf in your spec. You'll need to provide some more information