Issues

Modern parameter filters (ExactFilter, SortFilter, ComparisonFilter) generate invalid DQL for multi-word properties when a name converter is configured

#8380

· lglot opened

on Jul 2, 2026

Nullable arrays of BackedEnums or Objects are not properly deserialized

#8379

· MariusJam opened

on Jul 2, 2026

[MCP] tools/list returns empty list on api-platform/core 4.3.14–4.3.15 (4.3.13 OK)

#8370

· laryjulien opened

on Jun 30, 2026

Entrypoint leaks PHP FQCNs via resourceNameCollection in OpenAPI format

#8361

· RemcoSmitsDev opened

on Jun 28, 2026

use_symfony_listeners: true with read + input disabled leads to `Could not resolve argument $data`

#8354

· tandev opened

on Jun 26, 2026

Newly-added readable property on an existing resource is silently dropped from the (JSON-LD) output until var/cache is deleted; cache:clear does not invalidate it

#8332

· soyuka opened

on Jun 18, 2026

Strengthen JSON:API JSON Schema: full reserved-name handling + single source of truth for the attribute/relationship split

#8322

· soyuka opened

on Jun 17, 2026

Look into OpenAPI overlay specification

Feature

#8317

· soyuka opened

on Jun 17, 2026

Implement Arrazo OpenAPI specification

OpenAPI

Feature

#8316

· soyuka opened

on Jun 17, 2026

Global Default Parameters

#8315

· soyuka opened

on Jun 17, 2026

`object|<Class>` docblocks in `DispatchTrait` break metadata warmup under symfony/type-info 7.4 (`Cannot create union with both "object" and class type`)

#8312

· schmunk42 opened

on Jun 16, 2026

Expose URI variables to Link security expression

#8307

· rvanlaak opened

on Jun 16, 2026

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Uh oh!

Modern parameter filters (ExactFilter, SortFilter, ComparisonFilter) generate invalid DQL for multi-word properties when a name converter is configured

Nullable arrays of BackedEnums or Objects are not properly deserialized

[MCP] tools/list returns empty list on api-platform/core 4.3.14–4.3.15 (4.3.13 OK)

Entrypoint leaks PHP FQCNs via resourceNameCollection in OpenAPI format

use_symfony_listeners: true with read + input disabled leads to `Could not resolve argument $data`

Newly-added readable property on an existing resource is silently dropped from the (JSON-LD) output until var/cache is deleted; cache:clear does not invalidate it

Strengthen JSON:API JSON Schema: full reserved-name handling + single source of truth for the attribute/relationship split

Look into OpenAPI overlay specification

Implement Arrazo OpenAPI specification

Global Default Parameters

`object|<Class>` docblocks in `DispatchTrait` break metadata warmup under symfony/type-info 7.4 (`Cannot create union with both "object" and class type`)

Expose URI variables to Link security expression

Uh oh!

Uh oh!

Search results