Closed 1ed closed 1 year ago
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
I take this issue
still open as the fix was breaking #5540
Closing you've ways to fix this yourself now.
Closing you've ways to fix this yourself now.
could you please point to the place where it's documented? Sorry if I missed something
Declare the service yourself changing the priority doesn't work? We can still change priorities though it's out of the backward compatibility layer (though it may break some tests out there ^^)...
On 3.2 you can even decorate the ReadProvider
or the AccessCheckerProvider
to do this. It's hard to provide user-configuration over these priorities without overriding the dependency injection though.
API Platform version(s) affected: >=v2.3.0-beta.1
Description
I have a protected resource with a collection operation and a required integer filter. If I make a GET request without the filter and without an access token I get a 400 bad request instead of 401.
How to reproduce
See the description.
Possible Solution
The priority of the QueryParameterValidateListener seems to high to me, I think it should run just before the ReadListener at like priority 5.
Additional Context