Closed
Description
Q | A |
---|---|
Bug report? | yes? |
Feature request? | no |
BC Break report? | no |
Symfony version | all |
Context
In a Symfony app I'm disabling anything that I don't need. Fragments are one of those features.
I have this config:
framework:
fragments:
enabled: false
#esi: ~
Problem
In the appProdProjectContainer.php
container I still see a lot of things related to fragments:
1. Services
'fragment.handler' => 'getFragment_HandlerService',
'fragment.renderer.esi' => 'getFragment_Renderer_EsiService',
'fragment.renderer.hinclude' => 'getFragment_Renderer_HincludeService',
'fragment.renderer.inline' => 'getFragment_Renderer_InlineService',
'fragment.renderer.ssi' => 'getFragment_Renderer_SsiService',
2. Parameters
'fragment.renderer.hinclude.global_template' => NULL,
'fragment.path' => '/_fragment',
Moreover, there are some services that consider fragments mandatory:
<!-- @TwigBundle/Resources/config/twig.xml -->
<service id="twig.runtime.httpkernel" class="Symfony\Bridge\Twig\Extension\HttpKernelRuntime">
<argument type="service" id="fragment.handler" />
<tag name="twig.runtime" />
</service>
Solution
I expected all the fragment methods/params gone and the Twig service to use on-invalid="null"
.
Metadata
Metadata
Assignees
Labels
No labels