API Platform version(s) affected: 3.3.0
Description
After update from 3.2.22 to 3.3.0 my PATCH and PUT endpoints do not behave expected. The object is not loaded anymore, so my security context definitions fail.
How to reproduce
use ApiPlatform\Metadata as APM;
#[APM\ApiResource(
operations: [
new APM\Patch(
uriTemplate: '/users/{username}',
uriVariables: [
'clientId' => new APM\Link(toProperty: 'client', fromClass: Client::class),
'username' => new APM\Link(fromClass: User::class),
],
requirements: ['username' => '.+'],
status: Response::HTTP_ACCEPTED,
security: "is_granted('".Roles::FRONTEND_DEFAULT."')".
" and is_granted('".Roles::FRONTEND_CLIENT_READ."', object.getClient())".
" and is_granted('".Roles::FRONTEND_USER_UPDATE."', object)",
input: Update::class,
output: false,
processor: UpdateProcessor::class,
),
],
routePrefix: '/{clientId}',
)]
Possible Solution
I have no idea.
Additional Context
Occurs in dev mode on docker container and also in prod on live server
API Platform version(s) affected: 3.3.0
Description
After update from 3.2.22 to 3.3.0 my
PATCHandPUTendpoints do not behave expected. Theobjectis not loaded anymore, so my security context definitions fail.How to reproduce
Possible Solution
I have no idea.
Additional Context
Occurs in
devmode on docker container and also inprodon live server