askama - [no description]

	Commit message (Collapse)	Author	Age	Files	Lines
*	parser: add test for target recursion overflow	Dirkjan Ochtman	2024-01-11	1	-0/+6
\|
*	Yield a parser error when defining a macro named 'super'	Dirkjan Ochtman	2023-09-28	1	-0/+6
\|
*	Use char_indices() to get byte indices for characters	Dirkjan Ochtman	2023-09-11	1	-0/+7
\|
*	parser: better error message for unknown nodes	René Kijewski	2023-08-02	1	-1/+1
\|
*	parser: import `parser::{Expr, Node}`	René Kijewski	2023-08-01	1	-3/+2
\|
*	parser: add type for `Node::Comment`	René Kijewski	2023-08-01	1	-103/+52
\|
*	parser: remove re-exports `parser::{node,expr}::*`	René Kijewski	2023-08-01	1	-2/+4
\|
*	parser: add type for `Node::Lit`	René Kijewski	2023-08-01	1	-11/+5
\|
*	Fix parsing arrays	René Kijewski	2023-07-31	1	-0/+83
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	This change * allows using empty arrays `[]` in expessions, * adds a cut when the leading `[` was encountered, and * fixes the interaction between arrays and boolean OR. IMO the restriction that you couldn't use empty arrays is not needed. The missing cut made error messages slictly worse if you forget to add the closing `]`. Filter expressions must not have white spaces before the pipe `\|`. The white space is used to tell a filter expressions, and `std::ops::Or` apart.
*	Fix parsing calls	René Kijewski	2023-07-31	1	-1/+26
\| \| \| \| \| \| \|	This change: * adds a cut when the leading `(` was encountered, and * fixed the interaction between call expressions and boolean OR.
*	parser: add top-level Ast type	Dirkjan Ochtman	2023-07-31	1	-82/+108
\|
*	Extract askama_parser crate	Dirkjan Ochtman	2023-07-31	1	-0/+712