Bundle philosophy

[VincentClair]

I'm trying to understand core concepts of this bundle.
Could you please validate or invalidate my knowledge about it please ?

First, overblog/GraphQLBundle does not use directly persistence layer (or doctrine service - different from https://github.com/4rthem/graphql-mapper (-bundle) that it seems hardly couple with Doctrine). It uses services as resolver to fetch data (from database using doctrine or not, in memory, etc.).
In code examples, where it is called $humans = StarWarsData::humans();, I had to replace this by my entity repository for exemple.
In resolveFriend methods, I could replace StarWarsData::getFriends($character); by $character->getFriends() in traditional Symfony/Entity/Doctrine way.

As soon as i have a property with a listOf personal type, defining a object, i have to set a resolver, to tell bundle how to retreive data.

If I would like to expose the full list of my Characters, i declare the following Query object:

# This implements the following type system shorthand:
#   type Query {
#     characters(limit: Int, offset: Int, orderBy: String): [Character]
#   }
#
Query:
    type: object
    config:
        description: "Full list of characters in the Star Wars universe."
        fields:
            characters:
                type: "[Character]"
                args:
                    limit:
                        description: "If omitted,return 10 characters maximum"
                        type: "Int"
                    offset:
                        description: "If omitted, begin at 0"
                        type: "Int"
                    orderBy:
                        description: "If omitted, no sort applied"
                        type: "String"
                resolve: "@=service('acme_bundle.my_service').find([args])"

I set a different resolve expression to be sure to understand the way to use it.

Thanks for your help

[mcg-web]

When using the bundle you properties must be accessible publicly because of the default Resolver of the php lib https://github.com/webonyx/graphql-php/blob/c81605bfb196f1f64ee921df1c148c427d4467c1/src/Executor/Executor.php#L621-L637 . We can use ReflectionClass to bypass the limitation or you can also bypass it using some magic __get combine with __isset. To access using getter you can define your resolver like this:

friends:
    type: "[Character]"
    description: "The friends of the character."
    resolve: "@=value.getFriends()"

I'm going to override the default resolver to use reflection.

[VincentClair]

Thank you for your quick reply !

Effectively, all my object properties are private and only accessible by getters and setters.
It's a little painful now to set resolve at all properties. Can't wait your override on the default resolver ;)

By the while, this bundle rocks and help me a lot.

[VincentClair]

#4 works very well (tested on scalars, sub object, ArrayCollection).
Good job 👍