Download the PHP package ifcanduela/router without Composer
On this page you can find all versions of the php package ifcanduela/router. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download ifcanduela/router
More information about ifcanduela/router
Files in ifcanduela/router
Package router
Short Description A routing component wrapping FastRoute
License MIT
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package router
Router
PHP router wrapping nikic/fast-route, with support for nested route
groups, default parameters and a few other extra features.
Installation
Use Composer:
Usage
Create an ifcanduela\router\Router instance and define routes:
Loading routes from a file
Loading routes from a file is the preferred method to initialise a router. Create a
file like this, for example routes.php:
And load the file like this:
The second argument to loadRoute() defines the name of the router in the loaded file; the default is simply
router. Additionally, the $this metavariable is always available in the loaded file and refers to the
calling Group or Router.
Files can be loaded from nested groups also:
Route definitions
Routes are mostly created using Router or Group methods:
Behind the scenes, those methods call the static constructors in the Route class:
The get, post, put and delete methods create routes that only match requests
with the same HTTP method. The from method allows GET and POST by default, but
the Group::from method accepts more string arguments with the HTTP methods to
allow.
Additionally, it's possible to call the methods method on a route to override its
allowed methods:
Routes follow the syntax defined by nikic/fast-route,
so you can add parameters using curly braces and wrap segments in square brackets to make them
optional. It's also possible to add default values for optional parameters:
Route groups
When more than one route share a prefix or metadata, you can put them together inside a group. There are several ways to define groups, but all of them have the same result. First, the generic way, in which the group is treated as a router:
A more clear way is to use a callback to define the grouped routes:
Resolving the route
The router will need a path and a HTTP method to resolve a route. If no matching route is found, an exception is thrown.
Route metadata
It's possible to attach extra information to routes to better identify them and facilitate their use in the request/response cycle.
Route names
Routes can be identified by names, which can help later when creating URLs to them:
You can check if a path and method combination matches a route name:
Tagging routes (before/after)
Tagging routes is useful to run middleware before or after matching them.
A different way of tagging routes is by using namespaces:
If you are using tags for middleware, you can use global middleware (applied to all routes) by attaching it to the router itself:
Once the route is resolved, all applicable tags can be accessed using $route->getBefore()
and $route->getAfter().
License
MIT.
