Skip to content

Latest commit

 

History

History
64 lines (51 loc) · 2.25 KB

bundle-configuration.md

File metadata and controls

64 lines (51 loc) · 2.25 KB

How to configure the bundle (SF 4.1 OR SF 3.4/4.0)

Back to menu / Back to installation

Configure on SF 4.1 and greatest

This is the available configuration for the bundle

In config/packages/graphql_client.yaml

graphql_client:
    sources:
        paths: # Can be not configured
          queries: "" # By default it's ["{$this->kernelRootDir}/Resources/graphql/queries"]
          fragments: "" # By default it's ["{$this->kernelRootDir}/Resources/graphql/fragments"]
        extension: "" # By default it's ".graphql"
    api: # All thees elements must been configured 
        host: "" # The host
        uri: "" # The api uri to contact
        token: "" # The token generated by mutation on the api
    logging_enabled: false # If you want to log queries to see in the debug toolbar

In dev mode config/packages/dev/graphql_client.yaml

graphql_client_bundle:
    logging_enabled: true

No you can use the bundle. If you want to change the queries cache adapter, it's simple to do here

If you want to directly use the service, you can check the usage doc

Configure on SF 3.4 or 4.0

This is the available configuration for the bundle

In app/config/config.yml

graphql_client:
    sources:
        paths: # Can be not configured
          queries: "" # By default it's ["{$this->kernelRootDir}/Resources/graphql/queries"]
          fragments: "" # By default it's ["{$this->kernelRootDir}/Resources/graphql/fragments"]
        extension: "" # By default it's ".graphql"
    api: # All thees elements must been configured 
        host: "" # The host
        uri: "" # The api uri to contact
        token: "" # The token generated by mutation on the api
    logging_enabled: false # If you want to log queries to see in the debug toolbar

In dev mode app/config/config_dev.yml

graphql_client_bundle:
    logging_enabled: true

No you can use the bundle. If you want to change the queries cache adapter, it's simple to do here

If you want to directly use the service, you can check the usage doc