nickel::middleware!

macro_rules! middleware {
    (|$req:tt, mut $res:ident| <$data:path> $($b:tt)+) => { _middleware_inner!($req, $res, mut $res, <$data> $($b)+) };
    (|$req:tt, $res:ident| <$data:path> $($b:tt)+) => { _middleware_inner!($req, $res, $res, <$data> $($b)+) };
    (|$req:tt| <$data:path> $($b:tt)+) => { middleware!(|$req, _res| <$data> $($b)+) };
    (|$req:tt, mut $res:ident| $($b:tt)+) => { _middleware_inner!($req, $res, mut $res, $($b)+) };
    (|$req:tt, $res:ident| $($b:tt)+) => { _middleware_inner!($req, $res, $res, $($b)+) };
    (|$req:tt| $($b:tt)+) => { middleware!(|$req, _res| $($b)+) };
    ($($b:tt)+) => { middleware!(|_, _res| $($b)+) };
}

Macro to reduce the boilerplate required for using unboxed closures as Middleware due to current type inference behaviour.

In future, the macro should hopefully be able to be removed while having minimal changes to the closure's code.

Examples

use nickel::{Nickel, HttpRouter};
use std::sync::atomic::{AtomicUsize, Ordering};

let mut server = Nickel::new();

// Some shared resource between requests, must be `Sync + Send`
let visits = AtomicUsize::new(0);

server.get("/", middleware! {
    format!("{}", visits.fetch_add(1, Ordering::Relaxed))
});

server.listen("127.0.0.1:6767");

Type hinting

Sometimes type inference is unable to determine the datatype for the server, which can lead to a lot of extra type annotations. The middleware! macro supports annotating the macro so as to drive the inference allowing the handler code to remain with minimal annotations.

middleware! { |_request, _response| <MyServerData>
    // _response is of type Response<MyServerData>
    "Hello World"
}