build(deps): bump api-platform/core from 2.7.18 to 3.3.4

[dependabot]

Bumps api-platform/core from 2.7.18 to 3.3.4.

Release notes

Sourced from api-platform/core's releases.

v3.3.4

What's Changed

• fix(symfony): store original data without clone by @​soyuka in api-platform/core#6367
• fix(validation): ValidationException causes TypeError exception when called with $code=null by @​KernelMrex in api-platform/core#6375
• Add phpdoc to FilterInterface by @​stephanvierkant in api-platform/core#6381
• test: PATCH on controller w/ dto by @​soyuka in api-platform/core#6368
• fix(graphql): no validate on delete mutation by @​soyuka in api-platform/core#6388

New Contributors

• @​KernelMrex made their first contribution in api-platform/core#6375

Full Changelog: api-platform/core@v3.3.3...v3.3.4

v3.3.3

What's Changed

• fix(symfony): no read should throw on wrong uri variables by @​soyuka in api-platform/core#6357
• fix(state): no location header without output by @​soyuka in api-platform/core#6356
• fix(symfony): no read should not throw on wrong uri variables by @​soyuka in api-platform/core#6359
• fix(graphql): resolver before validation by @​soyuka in api-platform/core#6363

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

v3.3.2

What's Changed

• fix(symfony): define use_symfony_listeners by @​soyuka in api-platform/core#6344
• fix(symfony): set normalization context in request attributes by @​soyuka in api-platform/core#6345
• fix(state): read without output by @​soyuka in api-platform/core#6347
• docs: add guide for custom TagCollector service by @​usu in api-platform/core#6348
• fix(symfony): use_symfony_listeners before registering services by @​soyuka in api-platform/core#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.

... (truncated)

Changelog

Sourced from api-platform/core's changelog.

v3.3.4

Bug fixes

• 002d8e514 fix(validation): ValidationException causes TypeError exception when called with $code=null (#6375)
• 77a917f2a fix(metadata): resource class php doc (#6381)
• d809315fb fix(symfony): store original data without clone (#6367)
• fb7c4658c fix(test): canonicalizing json arrays (#6386)

v3.3.3

Bug fixes

• 10f24f7a1 fix(state): no location header without output (#6356)
• 20c9165f2 fix(symfony): no read should not throw on wrong uri variables (#6359)
• 4cd359d40 fix(graphql): resolver before validation (#6363)
• 9d159f4fa fix(symfony): no read shouldn't throw InvalidIdentifiers (#6357)

v3.3.2

Bug fixes

• 6f806f4ee fix(state): read without output (#6347)
• 735e1509e fix(symfony): set normalization context in request attributes (#6345)
• b4984126a fix(symfony): use_symfony_listeners before registering services (#6350)
• f63fd8101 fix(symfony): define use_symfony_listeners (#6344)

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.

When using GraphQl, with event_listeners_backward_compatibility_layer: true, mutation resolver gets called before validation, when using false (the future default) validation occurs on the user's input.

v3.3.1 (pre-release)

... (truncated)

Commits

• 2f4ecc8 docs: changelog 3.3.4
• 0706426 docs: 3.2.23 changelog
• 5212f54 fix(test): canonicalizing json arrays (#6386)
• c174bc3 docs: typo on "Test your API" guide (#6351)
• 4b7ddd0 fix(graphql): no validate on delete mutation (#6388)
• 3fb7231 test: PATCH on controller w/ dto (#6368)
• 77a917f fix(metadata): resource class php doc (#6381)
• 002d8e5 fix(validation): ValidationException causes TypeError exception when called w...
• d809315 fix(symfony): store original data without clone (#6367)
• 4a6378c docs(mercure): getOperation => get_operation
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
devtools	❌ Failed (Inspect)			May 27, 2024 2:48am

[dependabot]

Superseded by #367.