Antoine Bluchet

> Shouldn't use_symfony_listeners be false if event_listeners_backward_compatibility_layer is also set to false? Not really as `use_symfony_listeners: false` also breaks some behaviors for example attributes like `read`.

MainController is never used with listeners, when listeners are enabled we use the PlaceholderAction. Forget the `event_listeners_backward_compatibility_layer` it's not needed anymore, now you can just pick whether: - `symfony_use_listeners=true` uses...

shouldn't you add a `path` to the item operation? Does it show up on `bin/console debug:router`?

Indeed, not a huge fan but this allows to redirect http errors to the swagger ui when enabled, we can probably add a flag to disable this which would fix...

Mhh this is harder then I thought @taophp you should overwrite the service instead, this service is part of a decoration chain therefore if you don't call the chain you...

#6449 introduces the `_api_disable_swagger_provider` flag inside `extraProperties`. Will be available in the next release.

thanks for the detailed report, there's nothing that said that resolvers should happen before validation but I think it's a valid behavior, I added a new test for that.

Back to this, we need to find a solution, I think it's confusing that we validate the data that gets resolved as validation should occur on the user input. What...

Isn't the resolver supposedly have the same behavior as a provider? Anyways, I'm considering adding an option to validate after the resolver is being called, this would work for both...

Can you check my PR? It adds an `validateAfterResolver: true`