Add getter to retrieve configured routes

[weierophinney]

Per a comment detailing how to handle modules in the Expressive skeleton, we need to expose a getter to allow users/tooling to retrieve the routes. Since routes are already stored as a property of the Application instance, we can add the following:

/**
 * Retrieve the set of currently registered routes.
 *
 * @return Router\Route[]
 */
public function getRoutes()
{
    return $this->routes;
}

[Ocramius]

-1 on this: make it a service instead?

[weierophinney]

Routes are created and added when calling get(), post(), etc.; router implementations are not guaranteed to store the original instances. As such, the Application instance is the canonical location for storing them.

Knowing that, what would you recommend, @Ocramius ?

[Ocramius]

Ouch, don't see a way out of an accessor then 😥

…

On 11 Jan 2017 02:43, "weierophinney" ***@***.***> wrote: Routes are created and added when calling get(), post(), etc.; router implementations are not guaranteed to store the original instances. As such, the Application instance is the canonical location for storing them. Knowing that, what would you recommend, @Ocramius <https://github.com/Ocramius> ? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#421 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAJakBEsf9fDaIBntvHz9ljh3D4zndIJks5rRDPQgaJpZM4Lfi5F> .

[krzysiekpiasecki]

If I have understood the problem then "Visitor" ?

public function routes(RouteCollectorInterface $collector): RouteCollectorInterface;

[Ocramius]

@krzysiekpiasecki overkill for this scenario - I was just hoping for simply not expanding the API on the Application object, at all.

[weierophinney]

#426 resolves this and has been merged to the develop branch.