[Feat] allow omitting resolver alias in tag config about graphqlbundle HOT 4 CLOSED

Ok I understand the need, is true that the bundle require a lot of configuration, we must work on a flow to ease resolvers and mutations definitions.... In first step i added #133.

from graphqlbundle.

This feature has been added to master (release will comes later), here the doc. Thanks again for the idea 👍

from graphqlbundle.

I was about checking out to make a PR, this was the fastest reaction I ever experienced!

AppBundle\GraphQL\Resolver\WorkflowsResolver:
    class: AppBundle\GraphQL\Resolver\WorkflowsResolver
    tags:
      - { name: overblog_graphql.resolver, method: '__invoke', alias: 'AppBundle\GraphQL\Resolver\WorkflowsResolver' }

Should be defaulted from:

services:
  AppBundle\GraphQL\Resolver\WorkflowsResolver:
    class: AppBundle\GraphQL\Resolver\WorkflowsResolver
    tags:
      - { name: overblog_graphql.resolver }

This could be the default behavior without BC break. And with some extras, like the DunlasActionBundle it would be possible to auto-tag & wire so you don`t even need to provide this. I think it should not be be tied to another bundle, but it saves already boilerplate without. The usage of the bundle can be proposed in docs as a best practice to even save more, if you agree.

• Resolver/Mutation services become thin. They do not handle 100 different resolves/mutations: Concern separation.
• You don't have to write the config for resolver/mutation services.
• It is all compile time

from graphqlbundle.

This is awesome! Implementing this could helps win a lot of time. DunglasActionBundle is a good example...

from graphqlbundle.