<p dir="auto">I know the protected vs. private debate has been coming up several times already, yet my question: is there a reason not to make the <code class="notranslate">Filesystem</code> components <code class="notranslate">toIterator()</code> method <code class="notranslate">protected</code>? I'd like to extend the class in one project and keep the concept of allowing strings, arrays or any Traversables to be passed.</p>
<p dir="auto">There are quite a number of dependencies in symfony/framework-bundle that should be optional.</p>
<ol dir="auto">
<li>symfony/asset</li>
</ol>
<p dir="auto">Don't need it when building an app without GUI.</p>
<ol start="2" dir="auto">
<li>symfony/security-core</li>
</ol>
<p dir="auto">Don't need when I don't want to include any sort of access control</p>
<ol start="3" dir="auto">
<li>symfony/security-csrf</li>
</ol>
<p dir="auto">Don't need it unless I have forms. Which is an optional requirement in the form (pardon the pun) of symfony/form. Even if you keep security-core, this should go unless you have symfony-form.</p>
<ol start="4" dir="auto">
<li>doctrine/annotations</li>
</ol>
<p dir="auto">I may not want to use annotations.</p>
<ol start="5" dir="auto">
<li>symfony/translation</li>
</ol>
<p dir="auto">I might not care about translations</p>
<ol start="6" dir="auto">
<li>symfony/stopwatch</li>
</ol>
<p dir="auto">Why is this not in require-dev?</p>
<ol start="7" dir="auto">
<li>symfony/templating</li>
</ol>
<p dir="auto">Again, without a GUI I don't really need this.</p>
<p dir="auto">Anyone sharing this opinion or should I create my own symfony-minimal-framework-bundle if I want something less 'standard distribution'-like?</p>
<p dir="auto">Possible solution would be extracting the other deps into something like symfony/core-framework-bundle and have symfony/framework-bundle depend on that. Then packages depending on framework-bundle would not suddenly have to deal with missing deps.</p>