Struct perseus::ErrorPages

pub struct ErrorPages<G: Html> { /* private fields */ }

A type alias for the HashMap the user should provide for error pages.

Implementations

impl<G: Html> ErrorPages<G>

pub fn new(
    fallback: impl Fn(Scope<'_>, String, u16, String, Option<Rc<Translator>>) -> View<G> + Send + Sync + 'static
) -> Self

Creates a new definition of error pages with just a fallback.

pub fn add_page(
    &mut self,
    status: u16,
    page: impl Fn(Scope<'_>, String, u16, String, Option<Rc<Translator>>) -> View<G> + Send + Sync + 'static
)

Adds a new page for the given status code. If a page was already defined for the given code, it will be updated by the mechanics of the internal HashMap.

pub fn add_page_rc(&mut self, status: u16, page: ErrorPageTemplate<G>)

Adds a new page for the given status code. If a page was already defined for the given code, it will be updated by the mechanics of the internal HashMap. This differs from .add_page() in that it takes an Rc, which is useful for plugins.

impl ErrorPages<SsrNode>

pub fn render_to_string(
    &self,
    url: &str,
    status: u16,
    err: &str,
    translator: Option<Rc<Translator>>
) -> String

Renders the error page to a string. This should then be hydrated on the client-side. No reactive scope is provided to this function, it uses an internal one.

pub fn render_to_string_scoped(
    &self,
    cx: Scope<'_>,
    url: &str,
    status: u16,
    err: &str,
    translator: Option<Rc<Translator>>
) -> String

Renders the error page to a string, using the given reactive scope. Note that this function is not used internally, and .render_to_string() should cover all uses. This is included for completeness.

Trait Implementations

impl<G: Html> Debug for ErrorPages<G>

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.

impl<G: Html> Default for ErrorPages<G>

fn default() -> Self

Returns the “default value” for a type.