Maybe you should add a testHas() here: https://github.com/symfony/symfony/blob/master/src/Symfony/Component/Routing/Tests/RouteCollectionTest.php#L217)

Not 100% related to this PR, but never use Router#getRouteCollection(). This method will rebuilt all routing cache, meaning your application rebuilds routing cache each request and it'll be very slow: #7368

@wouterj, thanks for the heads up! So, there is no way to check whether a route exists at runtime...

@voronkovich yeah, catching the exception is knowing whether the route exists or not:

use Symfony\Component\Routing\Exception\RouteNotFoundException;

try {
    dump($router->generate('some_route'));
} catch (RouteNotFoundException $e) {
    dump('Oh noes, route "some_route" doesn't exists!');
}

Closing as as @wouterj mentioned, the route collection is an implementation detail that you should never use directly.

@fabpot do you know the reason why getRouteCollection() is part of the RouterInterface? (seems like you added it without any future references in 1467bdb ) To me, it seems like this one should not be part of any interface and marked as @internal on the Router class (it's only used on the debug commands and web profiler)

@wouterj That's very old :) I think this can be deprecated so that we can remove it in 4.0.

@wouterj the getRouteCollection was necessary for the old implementation of the router cache warming.