This introduces support for Tide by implementing `From` over markup.
Unlike other frameworks, Tide does not seem to provide e.g. a trait
which could instead be implemented. However as demonstrated, this
alternative results in a simple, ergonomic interface.

Consumers may leverage Tide support by using the "tide" feature.

Co-authored-by: Chris Wong <lambda.fairy@gmail.com>

2021-08-06 14:22:05 +10:00

3.7 KiB

Raw Blame History

Web framework integration

Maud includes support for these web frameworks: Actix, Iron, Rocket, Rouille, and Tide.

Actix

Actix support is available with the "actix-web" feature:

# ...
[dependencies]
maud = { version = "*", features = ["actix-web"] }
# ...

Actix request handlers can use a Markup that implements the actix_web::Responder trait.

use actix_web::{get, App, HttpServer, Result as AwResult};
use maud::{html, Markup};
use std::io;

#[get("/")]
async fn index() -> AwResult<Markup> {
    Ok(html! {
        html {
            body {
                h1 { "Hello World!" }
            }
        }
    })
}

#[actix_web::main]
async fn main() -> io::Result<()> {
    HttpServer::new(|| App::new().service(index))
        .bind(("127.0.0.1", 8080))?
        .run()
        .await
}

Iron

Iron support is available with the "iron" feature:

# ...
[dependencies]
maud = { version = "*", features = ["iron"] }
# ...

With this feature enabled, you can then build a Response from a Markup object directly. Here's an example application using Iron and Maud:

use iron::prelude::*;
use iron::status;
use maud::html;

fn main() {
    Iron::new(|r: &mut Request| {
        let markup = html! {
            h1 { "Hello, world!" }
            p {
                "You are viewing the page at " (r.url)
            }
        };
        Ok(Response::with((status::Ok, markup)))
    }).http("localhost:3000").unwrap();
}

Markup will set the content type of the response automatically, so you don't need to add it yourself.

Rocket

Rocket works in a similar way, except using the rocket feature:

# ...
[dependencies]
maud = { version = "*", features = ["rocket"] }
# ...

This adds a Responder implementation for the Markup type, so you can return the result directly:

#![feature(decl_macro)]

use maud::{html, Markup};
use rocket::{get, routes};
use std::borrow::Cow;

#[get("/<name>")]
fn hello<'a>(name: Cow<'a, str>) -> Markup {
    html! {
        h1 { "Hello, " (name) "!" }
        p { "Nice to meet you!" }
    }
}

fn main() {
    rocket::ignite().mount("/", routes![hello]).launch();
}

Rouille

Unlike with the other frameworks, Rouille doesn't need any extra features at all! Calling Response::html on the rendered Markup will Just Work®.

use maud::html;
use rouille::{Response, router};

fn main() {
    rouille::start_server("localhost:8000", move |request| {
        router!(request,
            (GET) (/{name: String}) => {
                Response::html(html! {
                    h1 { "Hello, " (name) "!" }
                    p { "Nice to meet you!" }
                })
            },
            _ => Response::empty_404()
        )
    });
}

Tide

Tide support is available with the "tide" feature:

# ...
[dependencies]
maud = { version = "*", features = ["tide"] }
# ...

This adds an implementation of From<PreEscaped<String>> for the Response struct. Once provided, callers may return results of html! directly as responses:

use maud::html;
use tide::Request;
use tide::prelude::*;

#[async_std::main]
async fn main() -> tide::Result<()> {
    let mut app = tide::new();
    app.at("/hello/:name").get(|req: Request<()>| async move {
        let name: String = req.param("name")?.parse()?;
        Ok(html! {
            h1 { "Hello, " (name) "!" }
            p { "Nice to meet you!" }
        })
    });
    app.listen("127.0.0.1:8080").await?;
    Ok(())
}

3.7 KiB Raw Blame History