Plume/templates/errors/base.rs.html

@use templates::base as base_template;
@use template_utils::*;

@(ctx: BaseContext, error_message: String, error: Content)

@:base_template(ctx, error_message.clone(), {}, {}, {
  @:error()
  <p>@error_message</p>
})
Use Ructe (#327) All the template are now compiled at compile-time with the `ructe` crate. I preferred to use it instead of askama because it allows more complex Rust expressions, where askama only supports a small subset of expressions and doesn't allow them everywhere (for instance, `{{ macro!() \| filter }}` would result in a parsing error). The diff is quite huge, but there is normally no changes in functionality. Fixes #161 and unblocks #110 and #273 2018-12-06 17:54:16 +00:00			`@use templates::base as base_template;`
			`@use template_utils::*;`

Update rocket_i18n and add gettext_macros (#431) Internationalization now uses proc-macros that generate the .pot file automatically. 2019-02-02 14:23:50 +00:00			`@(ctx: BaseContext, error_message: String, error: Content)`
Use Ructe (#327) All the template are now compiled at compile-time with the `ructe` crate. I preferred to use it instead of askama because it allows more complex Rust expressions, where askama only supports a small subset of expressions and doesn't allow them everywhere (for instance, `{{ macro!() \| filter }}` would result in a parsing error). The diff is quite huge, but there is normally no changes in functionality. Fixes #161 and unblocks #110 and #273 2018-12-06 17:54:16 +00:00
Update rocket_i18n and add gettext_macros (#431) Internationalization now uses proc-macros that generate the .pot file automatically. 2019-02-02 14:23:50 +00:00			`@:base_template(ctx, error_message.clone(), {}, {}, {`
Use Ructe (#327) All the template are now compiled at compile-time with the `ructe` crate. I preferred to use it instead of askama because it allows more complex Rust expressions, where askama only supports a small subset of expressions and doesn't allow them everywhere (for instance, `{{ macro!() \| filter }}` would result in a parsing error). The diff is quite huge, but there is normally no changes in functionality. Fixes #161 and unblocks #110 and #273 2018-12-06 17:54:16 +00:00			`@:error()`
			`<p>@error_message</p>`
			`})`