Are there any plans to support Swagger-PHP 3 now that it released? That's probably a significant undertaking considering the steps outlined in http://zircote.com/swagger-php/Migrating-to-v3.html and the 3.x branch was in development for quite some time.
I've worked with that project directly but there's a bit to unpack like how it defaults to outputting yaml instead of json though that can be changed. Swagger UI 3 supports both v2 and v3 definitions but I have to assume it doesn't parse yaml so it likely still needs the json output. The platform doesn't really seem to change all that much with the bulk of the changes being users updating their annotations but I probably haven't looked deep enough to realize how annoying it could be to work with.
If I had free time I could see how quickly it would be to work up a prototype using a simple site I have but my free time is non-existent these days 😦
Are there any plans to support Swagger-PHP 3 now that it released? That's probably a significant undertaking considering the steps outlined in http://zircote.com/swagger-php/Migrating-to-v3.html and the 3.x branch was in development for quite some time.
I've worked with that project directly but there's a bit to unpack like how it defaults to outputting yaml instead of json though that can be changed. Swagger UI 3 supports both v2 and v3 definitions but I have to assume it doesn't parse yaml so it likely still needs the json output. The platform doesn't really seem to change all that much with the bulk of the changes being users updating their annotations but I probably haven't looked deep enough to realize how annoying it could be to work with.
If I had free time I could see how quickly it would be to work up a prototype using a simple site I have but my free time is non-existent these days 😦