Struct trillium_handlebars::HandlebarsHandler [−][src]
pub struct HandlebarsHandler(_);
Expand description
A trillium handler that provides registered templates to downsequence handlers
Implementations
Builds a new trillium Handlebars handler from either a directory
glob string or PathBuf
or a
handlebars::Handlebars<'static>
instance
From a glob
use trillium_handlebars::{HandlebarsHandler, HandlebarsConnExt}; let handler = ( HandlebarsHandler::new("**/*.hbs"), |mut conn: trillium::Conn| async move { conn.assign("name", "handlebars") .render("examples/templates/hello.hbs") } ); use trillium_testing::prelude::*; assert_ok!(get("/").on(&handler), "hello handlebars!");
From a handlebars::Handlebars
use trillium_handlebars::{HandlebarsHandler, Handlebars, HandlebarsConnExt}; // building a Handlebars directly let mut handlebars = Handlebars::new(); handlebars.register_template_string("greet-user", "Hello {{name}}")?; let handler = ( HandlebarsHandler::new(handlebars), |mut conn: trillium::Conn| async move { conn.assign("name", "handlebars") .render("greet-user") } ); use trillium_testing::prelude::*; assert_ok!(get("/").on(&handler), "Hello handlebars");
Trait Implementations
Returns the “default value” for a type. Read more
Performs the conversion.
Executes this handler, performing any modifications to the Conn that are desired. Read more
Performes one-time async set up on a mutable borrow of the Handler before the server starts accepting requests. This allows a Handler to be defined in synchronous code but perform async setup such as establishing a database connection or fetching some state from an external source. This is optional, and chances are high that you do not need this. Read more
Performs any final modifications to this conn after all handlers have been run. Although this is a slight deviation from the simple conn->conn->conn chain represented by most Handlers, it provides an easy way for libraries to effectively inject a second handler into a response chain. This is useful for loggers that need to record information both before and after other handlers have run, as well as database transaction handlers and similar library code. Read more
predicate function answering the question of whether this Handler
would like to take ownership of the negotiated Upgrade. If this
returns true, you must implement Handler::upgrade
. The first
handler that responds true to this will receive ownership of the
trillium::Upgrade
in a subsequent call to Handler::upgrade
Read more
This will only be called if the handler reponds true to
Handler::has_upgrade
and will only be called once for this
upgrade. There is no return value, and this function takes
exclusive ownership of the underlying transport once this is
called. You can downcast the transport to whatever the source
transport type is and perform any non-http protocol communication
that has been negotiated. You probably don’t want this unless
you’re implementing something like websockets. Please note that
for many transports such as TcpStreams, dropping the transport
(and therefore the Upgrade) will hang up / disconnect. Read more
Auto Trait Implementations
impl RefUnwindSafe for HandlebarsHandler
impl Send for HandlebarsHandler
impl Sync for HandlebarsHandler
impl Unpin for HandlebarsHandler
impl UnwindSafe for HandlebarsHandler
Blanket Implementations
Mutably borrows from an owned value. Read more
pub fn vzip(self) -> V