Skip to content

fix(metadata): read hideHydraOperation and strictQueryParameterValidation on YAML resources and operations - #8719

Draft
Maxcastel wants to merge 1 commit into
api-platform:5.0from
Maxcastel:fix/yaml-hide-hydra-operation-strict-query-parameters
Draft

Maxcastel wants to merge 1 commit into
api-platform:5.0from
Maxcastel:fix/yaml-hide-hydra-operation-strict-query-parameters

Conversation

@Maxcastel

@Maxcastel Maxcastel commented Oct 16, 2026 •

Copy link
Copy Markdown
Contributor
Q A
Branch? 5.0
Tickets Related to #6871 #6399
License MIT

In YAML, hideHydraOperation and strictQueryParameterValidation didn't work everywhere (they do with attributes and XML):

resources:
    App\Entity\Book:
        strictQueryParameterValidation: true # ignored on the resource
        operations:
            ApiPlatform\Metadata\GetCollection:
                hideHydraOperation: true # ignored, it was read on the resource node

Both exist on ApiResource and on the operations, but the YAML extractor only read them on the operations (and hideHydraOperation from the wrong node).

They're now read on both, and an operation inherits the resource value, like the other options.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant