core

core copied to clipboard

Supersedes https://github.com/api-platform/core/pull/4363. Fixes an issue with the use of `EMPTY_ARRAY_AS_OBJECT` and `PRESERVE_EMPTY_OBJECTS` in the serialization context. Since the Hydra CollectionNormalizer was taking over the serialization of all iterables for the...

alanpoulain

| Q | A | ------------- | --- | Branch? | main | Tickets | n/a | License | MIT | Doc PR | todo Our current implementation of [the...

dunglas

fix(symfony): metadata cache is broken in dev/prod

8

| Q | A | ------------- | --- | Branch? | main | Tickets | #4975 | License | MIT Hi! Cache seems broken in 3.0.0. Metadatas are not stored...

emmanuelballery

fix(symfony): BC layer broken for symfony/console lower than 5.3

1

| Q | A | ------------- | --- | Branch? | 2.7 | Tickets | | License | MIT | Doc PR | BC layer for symfony/console

deguif

RFC-7807 compatible hydra error response

1

**Description** > Finally, the server SHOULD provide error descriptions using an [[RFC7807](https://www.hydra-cg.com/spec/latest/core/#bib-rfc7807)] standard by using an application/problem+json response. When doing so, the server also MUST provide an additional header pointing...

nesl247

**API Platform version(s) affected**: 3.0.0 **Description** Throwing an `AccountStatusException` in a `UserChecker` does not cause the response to occur in the appropriate error format as violation errors due. **Additional Context**...

nesl247

**Description** Currently custom errors do not have any identifiable information in them that a frontend application can check. Both Hydra via the `@id` (https://www.hydra-cg.com/spec/latest/core/#example-32-non-rfc-7807-compliant-error-description-using-raw-hydra-json-ld-representation) and RFC 7807 via `type` allow...

nesl247

[Provider] Inconsistent $uriVariables types

3

**API Platform version(s) affected**: 3.0.0 **Description** In Providers that implement `ProviderInterface` the `$uriVariables` array contains only `int` variables. If the `uriTemplate` receive a string, the received value in the provider...

mpiot

**API Platform version(s) affected**: 3.0.0 **Description** Swagger UI puts [object Object] to request instead of token. **How to reproduce** https://github.com/swagger-api/swagger-ui/issues/7926 **Possible Solution** Update to newer version. Fixed in [v4.8.1](https://github.com/swagger-api/swagger-ui/releases/tag/v4.8.1)

FVesely

Metadata cache uses `ArrayAdapter` instead of APCu

5

**API Platform version(s) affected**: 3.0.0 **Description** 3.0 uses `ArrayAdapter` as Metadata Cache. In 2.7 the default was to utilize APCu when it was installed. Was this changed by purpose? -->...

usu