GraphQl: cant disable operations with yaml

Hi iam using api/platform 3.0.7 and i want to modify graphql operations with yaml.

My yaml looks like this:

REST: i want only GET method GRAPHQL: i want enable only Query and Create mutation

Namespace\To\Entity:
    operations:
        ApiPlatform\Metadata\GetCollection: ~
        ApiPlatform\Metadata\Get: ~
    graphQlOperations:
        ApiPlatform\Metadata\GraphQl\Query: ~
        ApiPlatform\Metadata\GraphQl\Mutation:
            name: create

with REST (“operation” namespace) it works fine and i can see only GET methods. But with graphql i still can do collenctionQuery and all other mutations.

What am i doing wrong?

Thx for answer

[durimjusaj]

I have the same problem, after some research and debugging, I could find two issue related to this. ApiPlatform\Metadata\Extractor\YamlResourceExtractor => buildGraphQlOperations If collection is the first query in queries array, it will override all other queries as collection. I can see loop value overwritten in line 310 and 315 which are causing this problem.

ApiPlatform\Metadata\Resource\Factory\ExtractorResourceMetadataCollectionFactory => addGraphQlOperations attribute class is not filled, function addOperations has this getOperationWithDefaults which fixes name and other attributes, but is missing for graphql, this is why you have to specify class attribute in yaml directly.

my working yaml:

Namespace\To\Entity:
  operations: [ ]
  graphQlOperations:
    queries:
      ApiPlatform\Metadata\GraphQl\Query:
        class: Namespace\To\Entity
      ApiPlatform\Metadata\GraphQl\QueryCollection:
        collection: true
        class: Namespace\To\Entity

Also you can just send only array without operation class

Namespace\To\Entity:
  operations: [ ]
  graphQlOperations:
    queries:
      - class: Namespace\To\Entity
      - class: Namespace\To\Entity
        collection: true

[OndrosI]

@durimjusaj

Thank you, this works fine.

It would be nice to update documentation in next hotfix.