Incorrect ServiceCircularReferenceException?

[lmcd]

I've written a service that gets invoked inside a Twig template, which has a dependancy on the 'Templating' service. This results in a ServiceCircularReferenceException. Commenting out the exception causes the code to run fine.

[stof]

Circular references in the services can lead to incorrect creation of the objects, eventually leading to infinite loops. The issue is that each service requires the other one to be created before itself being created.
The correct way is to avoid circular references

[lmcd]

So my service must somehow be passed TwigEngine from within my twig template?

[fabpot]

The templating service relies on a lot of other services, so it is rather easy to have this circular dependency problem. You The exception should tell you for which service there is a problem. The solution depends on the service for which there is a circular reference problem, but one simple solution is to inject the container and get the service when you have a need for it.

[bmeynell]

It's been 3 years. It this possible yet (to not have to inject the container into a twig extension when you only need the templating service)?

[bmeynell]

It's been 3 years. It this possible yet (to not have to inject the container into a twig extension when you only need the templating service)?

Answering my own question here. I think I can use Twig_Environment::display() to accomplish rendering of a template from a twig extension.

[apfelbox]

@bmeynell I think what @fabpot was trying to say is that it is practically impossible: you need the twig service for the extension, but you need the extension for the twig service.

So you have the circular reference, as thrown.
load twig -> load extension -> load twig -> load extension -> ...

It would only be possible if the twig service is only loaded when you actually need it (instead of on creation time) - which you do by inserting the whole service container and requesting the service in your method.