Download the PHP package crazy-goat/router without Composer

CrazyGoat\Route - Crazy router for PHP, based on FastRoute

This library provides a fast implementation of a regular expression based router. Blog post explaining how the implementation works and why it is fast.
This fork add these crazy functions:

• middleware stack - add some middlewares to your route
• route generation - for named route you can generate a path
• pass max phpstan - possible less bugs :P

Install

To install with composer:

Requires PHP 7.1 or newer.

Usage

Here's a basic usage example:

Defining routes

The routes are defined by calling the CrazyGoat\Router\DispatcherFactory::createFromClosure() or function, which accepts a callable taking a CrazyGoat\Router\RouteCollector instance. The routes are added by calling addRoute() on the collector instance:

The $method is an uppercase HTTP method string for which a certain route should match. It is possible to specify multiple valid methods using an array:

By default the $routePattern uses a syntax where {foo} specifies a placeholder with name foo and matching the regex [^/]+. To adjust the pattern the placeholder matches, you can specify a custom pattern by writing {bar:[0-9]+}. Some examples:

Custom patterns for route placeholders cannot use capturing groups. For example {lang:(en|de)} is not a valid placeholder, because () is a capturing group. Instead you can use either {lang:en|de} or {lang:(?:en|de)}.

Furthermore parts of the route enclosed in [...] are considered optional, so that /foo[bar] will match both /foo and /foobar. Optional parts are only supported in a trailing position, not in the middle of a route.

The $handler parameter does not necessarily have to be a callback, it could also be a controller class name or any other kind of data you wish to associate with the route. CrazyGoat\Router only tells you which handler corresponds to your URI, how you interpret it is up to you.

Shortcut methods for common request methods

For the GET, POST, PUT, PATCH, DELETE and HEAD request methods shortcut methods are available. For example:

Is equivalent to:

Route Groups

Additionally, you can specify routes inside of a group. All routes defined inside a group will have a common prefix.

For example, defining your routes as:

Will have the same result as:

Nested groups are also supported, in which case the prefixes of all the nested groups are combined.

Caching

By using cachedDispatcher instead of simpleDispatcher you can cache the generated routing data and construct the dispatcher from the cached information:

First parameter is the file consist routing definitions. This file should return Closure with routing definition:

The second parameter is the path for file cache file. If cache file not exists, routing data is loaded from first parameter.

Dispatching a URI

A URI is dispatched by calling the dispatch() method of the created dispatcher. This method accepts the HTTP method and a URI. Getting those two bits of information (and normalizing them appropriately) is your job - this library is not bound to the PHP web SAPIs.

The dispatch() method returns an RouteInfo object which contains information about handler, variables and middleware stack. If none route match request uri the RouteNotFound exceptions is thrown. If route is found but method does not match request method the MethodNotAllowed exceptions will be thrown. You can get allowed methods from exceptions using calling getAllowedMethods() function.

NOTE: The HTTP specification requires that a 405 Method Not Allowed response include the Allow: header to detail available methods for the requested resource. Applications using CrazyGoat\Router should use the array from getAllowedMethods() to add this header when relaying a 405 response.

For the found status the RouteInfo object contains handler that was associated with the route, dictionary of placeholder names to their values and the middleware stack. For example:

Overriding the route parser and dispatcher

The routing process makes use of three components: A route parser, a data generator and a dispatcher. The three components adhere to the following interfaces:

The route parser takes a route pattern string and converts it into an array of route infos, where each route info is again an array of it's parts. The structure is best understood using an example:

/* The route /user/{id:\d+}[/{name}] converts to the following array: */
[
    [
        '/user/',
        ['id', '\d+'],
    ],
    [
        '/user/',
        ['id', '\d+'],
        '/',
        ['name', '[^/]+'],
    ],
]

This array can then be passed to the addRoute() method of a data generator. After all routes have been added the getData() of the generator is invoked, which returns all the routing data required by the dispatcher. The format of this data is not further specified - it is tightly coupled to the corresponding dispatcher.

The dispatcher accepts the routing data via a constructor or setData function and provides a dispatch() method, which you're already familiar with.

The route parser can be overwritten individually (to make use of some different pattern syntax), however the data generator and dispatcher should always be changed as a pair, as the output from the former is tightly coupled to the input of the latter. The reason the generator and the dispatcher are separate is that only the latter is needed when using caching (as the output of the former is what is being cached.)

To use custom parser, generator or dispatcher create new Configuration object and pass it to DispatcherFactory::prepareDispatcher() function:

Middleware

Adding middleware to route is very simple, just pass middleware paramter to addRoute() or addGroup() method in RouteCollecotr.

For the first route /users only root_middleware will be returned. For nested routes like /nested/users both middleware group_middleware and nested-middleware will be returned. You can also add more than one middleware to route:

Middleware stack is returned in routeInfo third index. If no middlewares where added to route an empty array will be returned.

Named routes and path generation

CrazyRoute provide an easy way to generate path for named route. First we must add a route with name. Name is passed as fifth parameter in addRoute() function. Route name must be unique else an exception BadRouteException will be thrown. Now all we have to do is call produce() function on Dispatcher object.

All required route params must be passed in second argument otherwise an exception will be thrown.

A Note on HEAD Requests

The HTTP spec requires servers to support both GET and HEAD methods:

The methods GET and HEAD MUST be supported by all general-purpose servers

To avoid forcing users to manually register HEAD routes for each resource we fallback to matching an available GET route for a given resource. The PHP web SAPI transparently removes the entity body from HEAD responses so this behavior has no effect on the vast majority of users.

However, implementers using CrazyGoat\Router outside the web SAPI environment (e.g. a custom server) MUST NOT send entity bodies generated in response to HEAD requests. If you are a non-SAPI user this is your responsibility; CrazyGoat\Router has no purview to prevent you from breaking HTTP in such cases.

Finally, note that applications MAY always specify their own HEAD method route for a given resource to bypass this behavior entirely.

Credits

This library is based on a FastRoute developed by Nikita Popov.

A large number of tests, as well as HTTP compliance considerations, were provided by Daniel Lowrey.