fix(graphql): use default nested query operations

[alanpoulain]

Instead of relying on a resource metadata factory to retrieve a "dynamic" nested query operation, this PR adds default nested query operations if the resource does not have one.

It simplifies a lot of things and catching the OperationNotFound exception is not needed anymore.

Since operations are "nested", they do not appear as top-level queries.

This PR also improves the XML/YAML compatibility.

[alanpoulain]

It seems to have been forgotten.
cc @vincentchalamon.

[alanpoulain]

It is needed since the IRI converter uses the operation name:

core/src/Symfony/Routing/IriConverter.php

Line 157 in f1ecc30

return $this->router->generate($operation->getName(), $identifiers, $operation->getUrlGenerationStrategy() ?? $referenceType);

In the previous version of the ExtractorResourceMetadataCollectionFactory, the name was overridden. The AttributesResourceMetadataCollectionFactory does not do that.
Does it mean we cannot customize the operation name @soyuka?

[soyuka]

yes we can change it, it should not be overriden

[soyuka]

but usually the name of the operation is used to define the one inside the router therefore this should work as welll

[alanpoulain]

Fixed!

[soyuka]

mb comment on Nested or here that this operation is then use when we fetch a query through another query

[alanpoulain]

Isn't the comment on the method sufficient?

[soyuka]

This is way better! Minor changes but then we can merge this!

[alanpoulain]

This was causing issues with the XML/YAML extractor (operations added twice), I think this modification improves the code (getOperationWithDefaults never called twice!).

[soyuka]

thanks @alanpoulain !

[develth]

i currently have the issue, that i query a single item with an id with nested Items.
As soon as i want to query the nested item, i get an Error from api-platform/core/src/Doctrine/Orm/State/ItemProvider.php:73 saying

More than one result was found for query although one row or none was expected.

Example Query:

query parentWithElements($parent: ID!) {
    parent(id: $parent) {
        id
        name
        elements{
            edges{
                node{
                    id
                    children{
                        edges{
                            node{
                                id
                                children{
                                    edges{
                                        node{
                                            id
                                        }
                                    }
                                }
                            }
                        }
                    }
                }
            }
        }
    }
}

Is that related or a new issue?