But it isn't scaleable. If somebody wants to create its own strategy? I.e.: take the documents description only if SeoMetadata is empy, but i implemented take documents description every time - as We have the discussion above. There are just nouances to the default strategies, but every custom behavior would mean to overide the service definition of the SeoPresentation. Or is there a chance to do that service injection more flexible? What do you think @dbu ?

Mit freundlichen Grüßen

Maximilian Berghoff


---------------------------------------
Maximilian Berghoff
Wiesenstraße 44
91617 Oberdachstetten 

Mail: Maximilian.berghoff@gmx.de
Mobile: +49 151 84625096

> On 14.03.2014, at 17:59, David Buchmann <notifications@github.com> wrote:
> 
> In DependencyInjection/Configuration.php:
> 
> > @@ -73,6 +74,14 @@ public function getConfigTreeBuilder()
> >                          ->end()
> >                      ->end()
> >                  ->end()
> > +                ->arrayNode('strategies')
> > +                    ->defaultValue(array(
> > +                            'Symfony\\Cmf\\Bundle\\SeoBundle\\Extractor\\SeoTitleStrategy',
> > +                            'Symfony\\Cmf\\Bundle\\SeoBundle\\Extractor\\SeoDescriptionStrategy',
> > +                            'Symfony\\Cmf\\Bundle\\SeoBundle\\Extractor\\SeoOriginalRouteStrategy',
> i think those should be services rather than class names - some strategy might have options, or need to be injected a service.
> 
> —
> Reply to this email directly or view it on GitHub.