Rocket/core/lib/src/codegen.rs

use handler::{Handler, ErrorHandler};
use http::{Method, MediaType};

pub struct StaticRouteInfo {
    pub name: &'static str,
    pub method: Method,
    pub path: &'static str,
    pub format: Option<MediaType>,
    pub handler: Handler,
    pub rank: Option<isize>,
}

pub struct StaticCatchInfo {
    pub code: u16,
    pub handler: ErrorHandler,
}
Namespace HTTP-related type under `http`. 2016-10-04 00:09:13 +00:00			`use handler::{Handler, ErrorHandler};`
Use MediaType instead of ContentType for Route format. 2017-03-28 07:12:59 +00:00			`use http::{Method, MediaType};`
HRTB for the win! Manual routes example fully working. 2016-04-03 10:36:30 +00:00
			`pub struct StaticRouteInfo {`
Propogate route names through codegen to runtime. This commit modifies `codegen` so that a route's name (the name of the route handler) is stored in the generated static route information structure and later propogated into the corresponding `Route` structure. The primary advantage of this change is an improvement to debug and error messages which now include route names. The collision error message, in particular, has been improved dramatically in this commit. Additionally, the `LaunchError::Collision` variant now contains a vector of the colliding routes. 2017-08-19 01:37:25 +00:00			`pub name: &'static str,`
HRTB for the win! Manual routes example fully working. 2016-04-03 10:36:30 +00:00			`pub method: Method,`
			`pub path: &'static str,`
Use MediaType instead of ContentType for Route format. 2017-03-28 07:12:59 +00:00			`pub format: Option<MediaType>,`
New type: ContentType. Parse ContentType from attribute. 2016-08-23 03:34:22 +00:00			`pub handler: Handler,`
Add `rank` to route attribute. Macrofy is_some ContentType methods. 2016-08-27 12:10:29 +00:00			`pub rank: Option<isize>,`
HRTB for the win! Manual routes example fully working. 2016-04-03 10:36:30 +00:00			`}`

Progress on error handling. Calling them 'catchers' for now. Added `error` decorator and `errors` macro. The current idea is that you can have "catchers" for all valid errors code (in range [400, 500). At the moment, catchers are just request handlers, and the decorator expected an empty function signature for the error handler. Obviously, this is pretty useless. Not sure on what the API should be here. But, progress. Oh, one more thing: who should handle forwarding a request to a catcher? Probably not the router. So, the main Rocket should? 2016-04-06 10:26:43 +00:00			`pub struct StaticCatchInfo {`
			`pub code: u16,`
Reform top-level libs mostly according to Rustfmt. 2016-09-30 22:20:11 +00:00			`pub handler: ErrorHandler,`
Progress on error handling. Calling them 'catchers' for now. Added `error` decorator and `errors` macro. The current idea is that you can have "catchers" for all valid errors code (in range [400, 500). At the moment, catchers are just request handlers, and the decorator expected an empty function signature for the error handler. Obviously, this is pretty useless. Not sure on what the API should be here. But, progress. Oh, one more thing: who should handle forwarding a request to a catcher? Probably not the router. So, the main Rocket should? 2016-04-06 10:26:43 +00:00			`}`