Antoine Bluchet

> It’s a bit more complex then just adding Dataproviders/persisters. There are pagination, filters and much more. Wish there was a guide on how to do this You want to...

It should work like other filters. What did you try?

> Should we add the filters property under the subresource operation too? Yes, or just use the ApiFilter annotation is should work seemlessly.

Nice report, thanks. Is this something we can fix in Api Platform?

I see an edge case and no real relation to Api Platform as ACL you're using here is part of symfony. Thanks for reporting this.

I think that someone already worked on using Laravel with Api Platform and it is definitely in our scope to make it work with other frameworks!

Nothing has been made AFAIK. First step would be to implement the Laravel Dependency Injection system for our classes (provider?). Then register the routes, just like we're doing with Symfony...

It's been almost 9 months and there's no breaking changes in OAS 3.1.x, what does it take to support it? https://github.com/swagger-api/swagger-ui/blob/cc408812fc927e265da158bf68239530740ab4cc/src/core/plugins/oas3/helpers.jsx#L9-L13

> There are breaking changes in OAS 3.1, specifically the JSON schema alignment where OAS 3.1 is now fully compatible with JSON Schema. I have to disagree as I was...

I don't really use swagger-ui but we bundle it inside API Platform and I'm trying to find a solution for everyone :). What can I do to help mainline gain...