<p dir="auto">How about throwing an exception if we're trying to declare a route with the name that already exists?</p>
<p dir="auto">For now it just silently does nothing, which doesn't help in development process at all.</p>
<table role="table">
<thead>
<tr>
<th>Q</th>
<th>A</th>
</tr>
</thead>
<tbody>
<tr>
<td>Bug report?</td>
<td>yes</td>
</tr>
<tr>
<td>Feature request?</td>
<td>no</td>
</tr>
<tr>
<td>BC Break report?</td>
<td>yes</td>
</tr>
<tr>
<td>RFC?</td>
<td>no</td>
</tr>
<tr>
<td>Symfony version</td>
<td>2.7.30, 2.8.23, 3.2.10, 3.3.3</td>
</tr>
</tbody>
</table>
<p dir="auto"><a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="236172654" data-permission-text="Title is private" data-url="https://github.com/symfony/symfony/issues/23195" data-hovercard-type="pull_request" data-hovercard-url="/symfony/symfony/pull/23195/hovercard" href="https://github.com/symfony/symfony/pull/23195">#23195</a> changed the assets:install command such that it removes unregonized content in the target directory.</p>
<p dir="auto">While I understand the intention, a feature that deletes files from disk (the webroot, even) without asking must not become the default behaviour in a patch level release.</p>
<p dir="auto">This change in behaviour broke our build/deployment scripts. Our AppKernel can be booted with different sets of bundles (controlled by an environment variable). So the build script does something like</p>
<div class="snippet-clipboard-content notranslate position-relative overflow-auto" data-snippet-clipboard-copy-content="THEME_A bin/console assets:install
THEME_B bin/console assets:install
THEME_C bin/console assets:install
# ..."><pre class="notranslate"><code class="notranslate">THEME_A bin/console assets:install
THEME_B bin/console assets:install
THEME_C bin/console assets:install
# ...
</code></pre></div>
<p dir="auto">Before <a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="236172654" data-permission-text="Title is private" data-url="https://github.com/symfony/symfony/issues/23195" data-hovercard-type="pull_request" data-hovercard-url="/symfony/symfony/pull/23195/hovercard" href="https://github.com/symfony/symfony/pull/23195">#23195</a> the resources for all themes were installed in the webroot, now only the resources required by the last configuration exist.</p>
<p dir="auto">It is also conceivable that people want to run completely unrelated Symfony applications out of the same webroot. Or the target path is on a remote filesystem, such as S3. Then running the command could break every other app.</p>
<p dir="auto">Please put this feature behind a --clean flag or so.</p>