Routing
Masonite Routing is an extremely simple but powerful routing system that at a minimum takes a url and a controller. Masonite will take this route and match it against the requested route and execute the controller on a match.
All routes are created inside routes/web.py and are contained in a ROUTES constant. All routes consist of some form of HTTP route classes (like Get() or Post()). At the bare minimum, a route will look like:
Get('/url/here', 'WelcomeController@show')
Most of your routes will consist of a structure like this. All URI’s should have a preceding /. Routes that should only be executed on Post requests (like a form submission) will look very similar:
Post('/url/here', 'WelcomeController@store')
Notice the controller here is a string. This is a great way to specify controllers as you do not have to import anything into your web.py file. All imports will be done in the backend. More on controllers later.
If you wish to not use string controllers and wish to instead import your controller then you can do so by specifying the controller as well as well as only passing a reference to the method. This will look like:
...from app.http.controllers.DashboardController import DashboardControllerROUTES = [Get('/url/here', DashboardController.show)]
It’s important here to recognize that we didn't initialize the controller or the method, we did not actually call the method. This is so Masonite can pass parameters into the constructor and method when it executes the route, typically through auto resolving dependency injection.
There are a few methods you can use to enhance your routes. Masonite typically uses a setters approach to building instead of a parameter approach so to add functionality, we can simply attach more methods.
There are several HTTP verbs you can use for routes:
from masonite.routes import Get, Post, Put, Patch, Delete, Match, Options, Trace, ConnectGet(..)Post(..)Put(..)Patch(..)Delete(..)Match(..)Options(..)Trace(..)Connect(..)
Some routes may be very similar. We may have a group of routes under the same domain, uses the same middleware or even start with the same prefixes. In these instances we should group our routes together so they are more DRY and maintainable.
We can add route groups like so:
from masonite.routes import RouteGroup, GetROUTES = [RouteGroup([Get('/url1', ...),Get('/url2', ...),Get('/url3', ...),]),]
This alone is great to group routes together that are similar but in addition to this we can add specific attributes to the entire group like adding middleware:
ROUTES = [RouteGroup([Get('/url1', ...),Get('/url2', ...),Get('/url3', ...),], middleware=('auth', 'jwt')),]
In the case you are only using one middleware:
ROUTES = [RouteGroup([Get('/url1', ...),Get('/url2', ...),Get('/url3', ...),], middleware=('auth',)),]
The , at the end of 'auth' ensures that it's treated as a tuple and not as an array of strings.
In this instance we are adding these 2 middleware to all of the routes inside the group. We have access to a couple of different methods. Feel free to use some or all of these options:
ROUTES = [RouteGroup([Get('/url1', ...).name('create'),Get('/url2', ...).name('update'),Get('/url3', ...).name('delete'),],middleware=('auth', 'jwt'),domain='subdomain',prefix='/dashboard',name='post.',add_methods=['OPTIONS']),]
The prefix parameter will prefix that URL to all routes in the group as well as the name parameter. The code above will create routes like /dashboard/url1 with the name of post.create. As well as adding the domain and middleware to the routes.
All of the options in a route group are named parameters so if you think adding a groups attribute at the end is weird you can specify them in the beginning and add the routes parameter:
RouteGroup(middleware=('auth', 'jwt'), name='post.', routes = [Get('/url1', ...).name('create'),Get('/url2', ...).name('update'),Get('/url3', ...).name('delete'),]),
Even more awesome is the ability to nest route groups:
ROUTES = [RouteGroup([Get('/url1', ...).name('create'),Get('/url2', ...).name('update'),Get('/url3', ...).name('delete'),RouteGroup([Get('/url4', ...).name('read'),Get('/url5', ...).name('put'),], prefix='/users', name='user.'),], prefix='/dashboard', name='post.', middleware=('auth', 'jwt')),]
This will go to each layer and generate a route list essentially from the inside out. For a real world example we refactor routes from this:
ROUTES = [Get().domain('www').route('/', 'WelcomeController@show').name('welcome'),Post().domain('www').route('/invite', 'InvitationController@send').name('invite'),Get().domain('www').route('/dashboard/apps', 'AppController@show').name('app.show').middleware('auth'),Get().domain('www').route('/dashboard/apps/create', 'AppController@create').name('app.create').middleware('auth'),Post().domain('www').route('/dashboard/apps/create', 'AppController@store').name('app.store'),Post().domain('www').route('/dashboard/apps/delete', 'AppController@delete').name('app.delete'),Get().domain('www').route('/dashboard/plans', 'PlanController@show').name('plans').middleware('auth'),Post().domain('www').route('/dashboard/plans/subscribe', 'PlanController@subscribe').name('subscribe'),Post().domain('www').route('/dashboard/plans/cancel', 'PlanController@cancel').name('cancel'),Post().domain('www').route('/dashboard/plans/resume', 'PlanController@resume').name('resume'),Post().domain('*').route('/invite', 'InvitationController@subdomain').name('invite.subdomain'),Get().domain('*').route('/', 'WelcomeController@subdomain').name('welcome'),]ROUTES = ROUTES + [Get().domain('www').route('/login', 'LoginController@show').name('login'),Get().domain('www').route('/logout', 'LoginController@logout'),Post().domain('www').route('/login', 'LoginController@store'),Get().domain('www').route('/register', 'RegisterController@show'),Post().domain('www').route('/register', 'RegisterController@store'),Get().domain('www').route('/home', 'HomeController@show').name('home'),]
into this:
ROUTES = [RouteGroup([# Dashboard RoutesRouteGroup([# App RoutesRouteGroup([Get('', 'AppController@show').name('show'),Get('/create', 'AppController@create').name('create'),Post('/create', 'AppController@store').name('store'),Post('/delete', 'AppController@delete').name('delete'),], prefix='/apps', name='app.'),Get('/plans', 'PlanController@show').name('plans'),Post('/plans/subscribe', 'PlanController@subscribe').name('subscribe'),Post('/plans/cancel', 'PlanController@cancel').name('cancel'),Post('/plans/resume', 'PlanController@resume').name('resume'),], prefix="/dashboard", middleware=('auth',)),# Login and Register RoutesGet('/login', 'LoginController@show').name('login'),Get('/logout', 'LoginController@logout'),Post('/login', 'LoginController@store'),Get('/register', 'RegisterController@show'),Post('/register', 'RegisterController@store'),Get('/home', 'HomeController@show').name('home'),# Base RoutesGet('/', 'WelcomeController@show').name('welcome'),Post('/invite', 'InvitationController@send').name('invite'),], domain='www'),# Subdomain invitation routesPost().domain('*').route('/invite', 'InvitationController@subdomain').name('invite.subdomain'),Get().domain('*').route('/', 'WelcomeController@subdomain').name('welcome'),]
This will likely be the most common way to build routes for your application.
You can also use View routes which is just a method on the normal route class:
ROUTES = [Get().view('/template', 'some/template', {'key': 'value'})]
You can use this view method with any route class.
You can also redirect right from the routes list using a Redirect route class:
from masonite.routes import RedirectROUTES = [Redirect('/old/route', '/new/route', status=302, methods=['GET', 'POST'])]
You do not have to specify the last 2 parameters. The default is a 302 response on GET methods.
You may have noticed above that we have a Match route class. This can match several incoming request methods. This is useful for matching a route with both PUT and PATCH.
Match(['PUT', 'PATCH']).route(...)
The request methods are not case sensitive. They will be converted to uppercase on the backend. So ['Put', 'Patch'] will work just fine
We can name our routes so we can utilize these names later when or if we choose to redirect to them. We can specify a route name like so:
Get('/dashboard', 'DashboardController@show').name('dashboard')
It is good convention to name your routes since route URI's can change but the name should always stay the same.
Middleware is a great way to execute classes, tasks or actions either before or after requests. We can specify middleware specific to a route after we have registered it in our config/middleware.py file but we can go more in detail in the middleware documentation. To add route middleware we can use the middleware method like so:
Get('/dashboard', 'DashboardController@show').middleware('auth', 'anothermiddleware')
This middleware will execute either before or after the route is executed depending on the middleware.
Read more about how to use and create middleware in the Middleware documentation.
All controllers are located in app/http/controllers but sometimes you may wish to put your controllers in different modules deeper inside the controllers directory. For example, you may wish to put all your product controllers in app/http/controllers/products or all of your dashboard controllers in app/http/controllers/users. In order to access these controllers in your routes we can simply specify the controller using our usual dot notation:
Get('/dashboard', 'users.DashboardController@show')
Controllers are defaulted to the app/http/controllers directory but you may wish to completely change the directory for a certain route. We can use a forward slash in the beginning of the controller namespace:
Get('/dashboard', '/thirdparty.package.users.DashboardController@show')
This can enable us to use controllers in third party packages.
You can also import the class directly and reference the method you want to use:
from app.controllers.SomeController import SomeControllerGet('/dashboard', SomeController.show)
Very often you’ll need to specify parameters in your route in order to retrieve information from your URI. These parameters could be an id for the use in retrieving a certain model. Specifying route parameters in Masonite is very easy and simply looks like:
Get('/dashboard/@id', 'Controller@show')
That’s it. This will create a dictionary inside the Request object which can be found inside our controllers.
In order to retrieve our parameters from the request we can use the param method on the Request object like so:
def show(self, request: Request):request.param('id')
Sometimes you want to optionally match routes and route parameters. For example you may want to match /dashboard/user and /dashboard/user/settings to the same controller method. In this event you can use optional parameters which are simply replacing the @ with a ?:
Get('/dashboard/user/?option', 'Controller@show')
You can also set default values if the route is not hit:
Get('/dashboard/user/?option', 'Controller@show').default({'option': 'settings'})
Sometimes you will want to make sure that the route parameter is of a certain type. For example you may want to match a URI like /dashboard/1 but not /dashboard/joseph. In order to do this we simply need to pass a type to our parameter. If we do not specify a type then our parameter will default to matching all alphanumeric and underscore characters.
Get('/dashboard/@id:int', 'Controller@show')
This will match all integers but not strings. So for example it will match /dashboard/10283 and not /dashboard/joseph
If we want to match all strings but not integers we can pass:
Get('/dashboard/@id:string', 'Controller@show')
This will match /dashboard/joseph and not /dashboard/128372. Currently only the integer and string types are supported.
These are called "Route Compilers" because they compile the route differently depending on what is specified. If you specify :int or :integer it will compile to a different regex than if you specified :string.
We can add route compilers to our project by specifying them in a Service Provider.
Make sure you add them in a Service Provider where wsgi is False. We can add them on the Route class from the container using the compile method. A completed example might look something like this:
from masonite.provider import ServiceProviderfrom masonite.routes import Routeclass RouteCompilerProvider(ServiceProvider):wsgi = False...def boot(self, route: Route):route.compile('year', r'([0-9]{4})')
We just need to call the compile() method on the Route class and make sure we specify a regex string by preceding an r to the beginning of the string.
Your regex should be encapsulated in a group. If you are not familiar with regex, this basically just means that your regex pattern should be inside parenthesis like the example above.
You may wish to only render routes if they are on a specific subdomain. For example you may want example.com/dashboard to route to a different controller than joseph.example.com/dashboard.
Out of the box this feature will not work and is turned off by default. We will need to add a call on the Request class in order to activate subdomains. We can do this in the boot method of one of our Service Providers that has wsgi=False:
wsgi = False...def boot(self, request: Request):request.activate_subdomains()
To use subdomains we can use the .domain() method on our routes like so:
Get().domain('joseph').route('/dashboard', 'Controller@show')
This route will match to joseph.example.com/dashboard but not to example.com/dashboard or test.example.com/dashboard.
It may be much more common to match any subdomain. For this we can pass in an asterisk instead.
Get().domain('*').route('/dashboard', 'Controller@show')
This will match all subdomains such as test.example.com/dashboard, joseph.example.com/dashboard but not example.com/dashboard.
If a match is found, it will also add a subdomain parameter to the Request class. We can retrieve the current subdomain like so:
def show(self, request: Request):print(request.param('subdomain'))
