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

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
api-platform/core (source)	3.2.4 -> 3.2.9

---

Release Notes

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

v3.2.9

Compare Source

What's Changed

• fix: Remove comparator conflict in 3.2 by @​jderusse in https://github.com/api-platform/core/pull/6063

Full Changelog: api-platform/core@v3.2.8...v3.2.9

v3.2.8

Compare Source

Bug fixes

• 2a43268f9 fix(jsonschema): fix invalid "int" type to "integer" (#​6049)
• 9660a190a fix(serializer): concat context on wrong id (#​6050)
• a35f0da11 fix(jsonld): remove link to ApiDocumentation when doc is disabled (#​6029)
• a9a06897b fix(doctrine): get reference with identifier value (#​6019)
• aac883e93 fix(symfony): bypass symfony exception listener (#​6056)
• b1926f533 fix(symfony): do not use metadata when merging schema constraints in Collection constraint (#​6057)
• cc16a1ced fix(jsonschema): iri example (#​5901)
• ccf52c199 fix: item_uri_template conflict with context on relation (#​6015)
• dcce75121 fix(doctrine): OrderFilterTrait - properties null value causing error in foreach
• dcfd3c5ca fix(jsonschema): keep format subschema generation (#​6055)
• c13c88e5c fix(metadata): throw exception if itemUriTemplate if used on invalid operation (xml/yaml formats) (#​6053)

v3.2.7

Compare Source

Symfony 7 support.

Bug fixes

• 183b4d637 fix(symfony): named arguments dependency injection
• 3d32d5e12 fix(openapi): entrypoint access vnd+openapi (#​6012)
• 58f4a3dda fix: no boolean types for exclusive minimum and exclusive maximum open api (#​5993)
• 5e8f5eb99 fix(graphql): consider writable flag also for nested input types (#​5954)
• 9848bd4d4 fix: missing eager joins on to-one relationships (#​5992)
• aa44dd726 fix(openapi): max cardinality
• c2be40994 fix(symfony): error in provider without uri variables (#​6005)
• d2f281eed fix(jsonschema): fix recursive documentation when using a dto entity wrapper (#​5973)
• e7bc2ab57 fix(jsonschema): indirect resource input schema (#​6001)

v3.2.6

Compare Source

Bug fixes

To have errors backward compatible with 3.1, use:

api_platform:
    defaults:
         extra_properties:
             rfc_7807_compliant_errors: false

New extension points are available using Errors with rfc_7807_compliant_errors: true such as Error provider and Error Resource

• 1b4289412 fix: errors bc with rfc_7807_compliant_errors false (#​5974)
• ce297e6f7 fix(jsonschema): child entity property schema generation (#​5988) (#​5989)

v3.2.5

Compare Source

Full Changelog: api-platform/core@v3.2.4...v3.2.5

---

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.

---

• Branch has one or more failed status checks

[BacLuc]

Failure may be related to api-platform/core#5961
(and for the future: api-platform/core#5963)

[renovate]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠ Warning: custom changes will be lost.

[usu]

Failure may be related to api-platform/core#5961 (and for the future: api-platform/core#5963)

Api-platform 3.2 introduced some breaking changes on the format of error responses. We fixed these BCs with #3985.

Upstream, the BCs have now been fixed in api-platform/core#5974, hence I reverted our own changes as well.

see commit 2bb6fbc

[usu]

Another issue was introduced with api-platform/core#5901

IRI-references without a specific example value provided by us now contain "https://example.com". This messes up the automatic payload generation for our API tests. It's an easy fix for the tests, as we can easily override the example values.

However, this also has an effect on the generated OpenAPI output (see snapshot changes). Might be worth to look through to them to verify if we're still ok with this, or whether there's any upstream issue we want to trigger.

[BacLuc]

I find it strange that the descriptions of the derived models are now missing,
but not of all derived models, but when then only of derived models.
For me it is ok if we make the update first and then try to fix the documentation again

[github-actions]

⛔ Feature branch deployment currently inactive.

If the PR is still open, you can add the deploy! label to this PR to trigger a feature branch deployment.