@@ -94,7 +94,7 @@ class, you can add all the logic related to processing the configuration in that
9494 // use it directly to configure the service container (when defining an
9595 // extension class, you also have to do this merging and processing)
9696 $containerConfigurator->services()
97- ->get('acme.social .twitter_client')
97+ ->get('acme_social .twitter_client')
9898 ->arg(0, $config['twitter']['client_id'])
9999 ->arg(1, $config['twitter']['client_secret'])
100100 ;
@@ -343,7 +343,7 @@ For example, imagine your bundle has the following example config:
343343 https://symfony.com/schema/dic/services/services-1.0.xsd"
344344 >
345345 <services >
346- <service id =" acme.social .twitter_client" class =" Acme\SocialBundle\TwitterClient" >
346+ <service id =" acme_social .twitter_client" class =" Acme\SocialBundle\TwitterClient" >
347347 <argument ></argument > <!-- will be filled in with client_id dynamically -->
348348 <argument ></argument > <!-- will be filled in with client_secret dynamically -->
349349 </service >
@@ -366,7 +366,7 @@ In your extension, you can load this and dynamically set its arguments::
366366 $configuration = new Configuration();
367367 $config = $this->processConfiguration($configuration, $configs);
368368
369- $definition = $container->getDefinition('acme.social .twitter_client');
369+ $definition = $container->getDefinition('acme_social .twitter_client');
370370 $definition->replaceArgument(0, $config['twitter']['client_id']);
371371 $definition->replaceArgument(1, $config['twitter']['client_secret']);
372372 }
0 commit comments