Controllers
Loco
is a framework that wraps around axum, offering a straightforward approach to manage routes, middlewares, authentication, and more right out of the box. At any point, you can leverage the powerful axum Router and extend it with your custom middlewares and routes.
Controllers and Routing
Adding a controller
Provides a convenient code generator to simplify the creation of a starter controller connected to your project. Additionally, a test file is generated, enabling easy testing of your controller.
Generate a controller:
After generating the controller, navigate to the created file in src/controllers
to view the controller endpoints. You can also check the testing (in folder tests/requests) documentation for testing this controller.
Displaying active routes
To view a list of all your registered controllers, execute the following command:
This command will provide you with a comprehensive overview of the controllers currently registered in your system.
Adding state
Your app context and state is held in AppContext
and is what Loco provides and sets up for you. There are cases where you'd want to load custom data,
logic, or entities when the app starts and be available to use in all controllers.
You could do that by using Axum's Extension
. Here's an example for loading an LLM model, which is a time consuming task, and then providing it to a controller endpoint, where its already loaded, and fresh for use.
First, add a lifecycle hook in src/app.rs
:
// in src/app.rs, in your Hooks trait impl override the `after_routes` hook:
async
Next, consume this state extension anywhere you like. Here's an example controller endpoint:
async
Routes in Controllers
Controllers define Loco routes capabilities. In the example below, a controller creates one GET endpoint and one POST endpoint:
use ;
new
.add
.add
You can also define a prefix
for all routes in a controller using the prefix
function.
Sending Responses
Response senders are in the format
module. Here are a few ways to send responses from your routes:
// keep a best practice of returning a `Result<impl IntoResponse>` to be able to swap return types transparently
pub async json
// use `render` for a builder interface for more involved responses. you can still terminate with
// `json`, `html`, or `text`
render
.etag?
.json
Content type aware responses
You can opt-in into the responders mechanism, where a format type is detected and handed to you.
Use the Format
extractor for this:
pub async
Custom errors
Here is a case where you might want to both render differently based on different formats AND ALSO, render differently based on kinds of errors you got.
pub async
Here, we also "centralize" our error handling by first wrapping the workflow in a function, and grabbing the result type.
Next we create a 2 level match to:
- Match the result type
- Match the format type
Where we lack the knowledge for handling, we just return the error as-is and let the framework render out default errors.
Creating a Controller Manually
1. Create a Controller File
Start by creating a new file under the path src/controllers
. For example, let's create a file named example.rs
.
2. Load the File in mod.rs
Ensure that you load the newly created controller file in the mod.rs
file within the src/controllers
folder.
3. Register the Controller in App Hooks
In your App hook implementation (e.g., App struct), add your controller's Routes
to AppRoutes
:
// src/app.rs
;
Middleware
Compression
Loco
leverages CompressionLayer to enable a one click
solution.
To enable response compression, based on accept-encoding
request header, simply edit the configuration as follows:
#...
middlewares:
compression:
enable: true
Doing so will compress each response and set content-encoding
response header accordingly.
Prcompressed assets
Loco
leverages ServeDir::precompressed_gzip to enable a one click
solution of serving pre compressed assets.
If a static assets exists on the disk as a .gz
file, Loco
will serve it instead of compressing it on the fly.
#...
middlewares:
...
static_assets:
...
precompressed: true
Pagination
In many scenarios, when querying data and returning responses to users, pagination is crucial. In Loco
, we provide a straightforward method to paginate your data and maintain a consistent pagination response schema for your API responses.
Using pagination
use *;
let pagination_query = PaginationQuery ;
let condition = condition.contains;
let paginated_notes = paginate
.await?;
- Start by defining the entity you want to retrieve.
- Create your query condition (in this case, filtering rows that contain "loco" in the title column).
- Define the pagination parameters.
- Call the paginate function.
Pagination view
After creating getting the paginated_notes
in the previous example, you can choose which fileds from the model you want to return and keep the same pagination response in all your different data responses.
Define the data you're returning to the user in Loco views. If you're not familiar with views, refer to the documentation for more context.
Create a notes view file in src/view/notes
with the following code:
use ;
use ;
use crate notes;
Testing
When testing controllers, the goal is to call the router's controller endpoint and verify the HTTP response, including the status code, response content, headers, and more.
To initialize a test request, use testing::request
, which prepares your app routers, providing the request instance and the application context.
In the following example, we have a POST endpoint that returns the data sent in the POST request.
async
As you can see initialize the testing request and using request
instance calling /example endpoing.
the request returns a Response
instance with the status code and the response test