You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The config file should gain a subtable in which the user can specify Jinja templates for rendering each event type and the e-mail as a whole.
The event details should be present in an event template's context as an event: reponews.types.Event variable.
The template for the e-mail as a whole should be passed the events as an events: List[reponews.types.Event] variable, and each individual event is templated by calling a special render filter on it (not to be confused with Jinja's render() method; rethink name).
Strip trailing newlines from each template after rendering?
The templating subtable should have an environment_options (Rethink name) subtable giving parameters that will be passed directly to jinja2.Environment.
The templating subtable should have an html = BOOL key (default false) that, when set, causes reponews to use HTML instead of plain text templates as the default templates and also causes the final e-mail to be declared with Content-Type: text/html.
The config file should gain a subtable in which the user can specify Jinja templates for rendering each event type and the e-mail as a whole.
event: reponews.types.Event
variable.events: List[reponews.types.Event]
variable, and each individual event is templated by calling a specialrender
filter on it (not to be confused with Jinja'srender()
method; rethink name).environment_options
(Rethink name) subtable giving parameters that will be passed directly tojinja2.Environment
.html = BOOL
key (default false) that, when set, causesreponews
to use HTML instead of plain text templates as the default templates and also causes the final e-mail to be declared withContent-Type: text/html
.NewForkEvent
should gain auser
property that just returns.fork.owner
.The text was updated successfully, but these errors were encountered: