fix(deps): update dependency api-platform/core to v3.3.2

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
api-platform/core (source)	3.3.0 -> 3.3.2

---

Release Notes

api-platform/core (api-platform/core)

v3.3.2

Compare Source

What's Changed

• fix(symfony): define use_symfony_listeners by @​soyuka in https://github.com/api-platform/core/pull/6344
• fix(symfony): set normalization context in request attributes by @​soyuka in https://github.com/api-platform/core/pull/6345
• fix(state): read without output by @​soyuka in https://github.com/api-platform/core/pull/6347
• docs: add guide for custom TagCollector service by @​usu in https://github.com/api-platform/core/pull/6348
• fix(symfony): use_symfony_listeners before registering services by @​soyuka in https://github.com/api-platform/core/pull/6350

Notes

You can remove the event_listeners_backward_compatibility_layer flag and set use_symfony_listeners instead. The use_symfony_listeners should be true if you use controllers or if you rely on Symfony event listeners.

Note that now flags like read can be forced to true if you want to call a Provider even on POST operations. These are the rules we set up on runtime if no value has been set:

if (null === $operation->canValidate()) {
    $operation = $operation->withValidate(!$request->isMethodSafe() && !$request->isMethod('DELETE'));
}

if (null === $operation->canRead()) {
    $operation = $operation->withRead($operation->getUriVariables() || $request->isMethodSafe());
}

if (null === $operation->canDeserialize()) {
    $operation = $operation->withDeserialize(\in_array($operation->getMethod(), ['POST', 'PUT', 'PATCH'], true));
}

Previously listeners did the checks before reading our flags and you could not force the values.

Full Changelog: api-platform/core@v3.3.0...v3.3.1

Full Changelog: api-platform/core@v3.3.0...v3.3.2

v3.3.1

Compare Source

What's Changed

• fix(symfony): define use_symfony_listeners by @​soyuka in https://github.com/api-platform/core/pull/6344
• fix(symfony): set normalization context in request attributes by @​soyuka in https://github.com/api-platform/core/pull/6345
• fix(state): read without output by @​soyuka in https://github.com/api-platform/core/pull/6347
• docs: add guide for custom TagCollector service by @​usu in https://github.com/api-platform/core/pull/6348

Notes

You can remove the event_listeners_backward_compatibility_layer flag and set use_symfony_listeners instead. The use_symfony_listeners should be true if you use controllers or if you rely on Symfony event listeners.

Note that now flags like read can be forced to true if you want to call a Provider even on POST operations. These are the rules we set up on runtime if no value has been set:

if (null === $operation->canValidate()) {
    $operation = $operation->withValidate(!$request->isMethodSafe() && !$request->isMethod('DELETE'));
}

if (null === $operation->canRead()) {
    $operation = $operation->withRead($operation->getUriVariables() || $request->isMethodSafe());
}

if (null === $operation->canDeserialize()) {
    $operation = $operation->withDeserialize(\in_array($operation->getMethod(), ['POST', 'PUT', 'PATCH'], true));
}

Previously listeners did the checks before reading our flags and you could not force the values.

Full Changelog: api-platform/core@v3.3.0...v3.3.1

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate. View repository job log here.

[renovate]

Branch automerge failure

This PR was configured for branch automerge. However, this is not possible, so it has been raised as a PR instead.