<p dir="auto">Hey guys!</p>
<p dir="auto">I've noticed a possible inconsistency today. The setup is simple: import two routes with the same name but different patterns from different resource files (so that they don't YAML-override). For example:</p>
<div class="snippet-clipboard-content notranslate position-relative overflow-auto" data-snippet-clipboard-copy-content="# some routing.yml that's imported
foo_page:
    pattern:  /foo
    defaults: { _controller: MainBundle:Default:homepage }

# some other routing.yml that's imported
foo_page:
    pattern:  /second-foo-page
    defaults: { _controller: MainBundle:Default:homepage }"><pre class="notranslate"><code class="notranslate"># some routing.yml that's imported
foo_page:
    pattern:  /foo
    defaults: { _controller: MainBundle:Default:homepage }

# some other routing.yml that's imported
foo_page:
    pattern:  /second-foo-page
    defaults: { _controller: MainBundle:Default:homepage }
</code></pre></div>
<ul dir="auto">
<li>when the matcher is dumped, both routes appear, but the first pattern appears first</li>
<li>when the generator is dumped, only the second route appears, and is used for all generation</li>
</ul>
<p dir="auto">I believe the proper behavior should be that only the second route is used in the matcher, to be consistent with the dumper.</p>
<p dir="auto">Thanks!</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>no</td>
</tr>
<tr>
<td>RFC?</td>
<td>no</td>
</tr>
<tr>
<td>Symfony version</td>
<td>3.3.4</td>
</tr>
</tbody>
</table>
<p dir="auto">When attempting to run <code class="notranslate">./bin/console server:run</code> after having generated a bundle using <code class="notranslate">./bin/console generate:bundle --namespace=Acme/MyBundle --bundle-name=AcmeMyBundle --format=annotation</code> I get a <code class="notranslate">ClassNotFoundException</code>.</p>
<p dir="auto">If I update the <code class="notranslate">autoload psr-4</code> section of <code class="notranslate">composer.json</code> to include my bundle it all works fine.  I didn't have to do this in <code class="notranslate">3.3.2</code>.</p>