rocket_include_tera/debug/
macros.rs

1/// Used in the fairing of `TeraResponse` to include Tera files into your executable binary file. You need to specify each file's name and its path relative to the directory containing the manifest of your package. In order to reduce the compilation time and allow to hot-reload templates, files are compiled into your executable binary file together, only when you are using the **release** profile.
2#[macro_export]
3macro_rules! tera_resources_initialize {
4    ( $tera:expr, $($name:expr => $path:expr), * $(,)* ) => {
5        {
6            use ::std::collections::HashSet;
7
8            let mut set: HashSet<&'static str> = HashSet::new();
9
10            $(
11                if set.contains($name) {
12                    panic!("The name `{}` is duplicated.", $name);
13                } else {
14                    $tera.register_template_file($name, $crate::manifest_dir_macros::not_directory_path!($path)).unwrap();
15
16                    set.insert($name);
17                }
18            )*
19        }
20    };
21}
22
23/// Used for wrapping a `TeraResponse` and its constructor, and use a **key** to cache its HTML and ETag in memory. The cache is generated only when you are using the **release** profile.
24#[macro_export]
25macro_rules! tera_response_cache {
26    ($cm:expr, $etag_if_none_match:expr, $key:expr, $gen:block) => {{
27        #[allow(unused_variables)]
28        let __a = &$cm;
29        #[allow(unused_variables)]
30        let __a = &$key;
31
32        let res = $gen;
33
34        if res.weak_eq(&$etag_if_none_match) { $crate::TeraResponse::not_modified() } else { res }
35    }};
36}
rocket_include_tera/debug/macros.rs

rocket_include_tera/debug/
macros.rs
