@@ -98,7 +98,7 @@ class, you can add all the logic related to processing the configuration in that
98
98
// use it directly to configure the service container (when defining an
99
99
// extension class, you also have to do this merging and processing)
100
100
$containerConfigurator->services()
101
- ->get('acme.social .twitter_client')
101
+ ->get('acme_social .twitter_client')
102
102
->arg(0, $config['twitter']['client_id'])
103
103
->arg(1, $config['twitter']['client_secret'])
104
104
;
@@ -347,7 +347,7 @@ For example, imagine your bundle has the following example config:
347
347
https://symfony.com/schema/dic/services/services-1.0.xsd"
348
348
>
349
349
<services >
350
- <service id =" acme.social .twitter_client" class =" Acme\SocialBundle\TwitterClient" >
350
+ <service id =" acme_social .twitter_client" class =" Acme\SocialBundle\TwitterClient" >
351
351
<argument ></argument > <!-- will be filled in with client_id dynamically -->
352
352
<argument ></argument > <!-- will be filled in with client_secret dynamically -->
353
353
</service >
@@ -370,7 +370,7 @@ In your extension, you can load this and dynamically set its arguments::
370
370
$configuration = new Configuration();
371
371
$config = $this->processConfiguration($configuration, $configs);
372
372
373
- $definition = $container->getDefinition('acme.social .twitter_client');
373
+ $definition = $container->getDefinition('acme_social .twitter_client');
374
374
$definition->replaceArgument(0, $config['twitter']['client_id']);
375
375
$definition->replaceArgument(1, $config['twitter']['client_secret']);
376
376
}
0 commit comments