Routes are defined in controller classes, which are then connected to the router. You will add different routes as class names and then you will run the router:
Router::addClass(App\HomeController::class)Router::run()
The first method sets up some application endpoints and the latter method runs the application. An Exception is thrown if no valid endpoint is found.
The router instance is looking for the tags route and verbs using the attribute Route. A simple controller example could look like this:
The route will accept the verbs GET and POST and the path / will dispatch the method index.
The second route using the path /user/:username will dispatch the method userGreeting. This method transforms the second URL segment into a string parameter, which the controller method may use. This route only accepts GET requests (which is used if no verbs is used).
The path can also be made a bit more complex, like e.g. /user/:username/actions/:action. If this route is matched, then the Request will contain both username and action keys and values.
Let's connect the above SimpleHomeController class to a router instance in an index.php file:
Run the above example:
php -S localhost:8000 -t examples/router_simple
If you visit http://localhost:8000, you should receive a response from the server saying hello world!
If you visit http://localhost:8000/user/helen, you should receive a response saying Hello world helen!
If you visit a route that is not defined, you may get a 500 error without any useful message, but this depends on your server configuration.
We will make a setup in order to catch all errors. This will also deliver a better user experience:
You may run this example:
php -S localhost:8000 -t examples/router_error
If you visit http://localhost:8000/does/not/exists, you will get a message saying The page does not exist
You will also get a better trace of the error.
You may add middleware to you application. Middleware are just callables which will be called before hitting the controller method. You may specify multiple middleware callables.
Middleware are called in the order that they are added to your Router instance. The middleware callables will receive the same $request parameter as your controller.
Here is a controller where we expect a message to be set on the $request object:
Create an application like this:
Run the example:
php -S localhost:8000 -t examples/router_middleware
If you visit http://localhost:8000/user/helen, you should get the following response:
Hello world helen!
From middle_ware_2
Current route is: /user/:username