Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | Create a type alias for all `IResult` to simplify code reading | Guillaume Gomez | 2023-10-25 | 1 | -29/+23 |
| | |||||
* | Create `ErrorContext` type | Guillaume Gomez | 2023-10-25 | 1 | -33/+41 |
| | |||||
* | Require Expr::parse() callers to supply Level | Dirkjan Ochtman | 2023-09-28 | 1 | -10/+6 |
| | |||||
* | Move Level into the crate root | Dirkjan Ochtman | 2023-09-28 | 1 | -16/+1 |
| | |||||
* | Limit expression nesting level to avoid stack overflows | Dirkjan Ochtman | 2023-09-28 | 1 | -33/+81 |
| | |||||
* | Use char_indices() to get byte indices for characters | Dirkjan Ochtman | 2023-09-11 | 1 | -1/+1 |
| | |||||
* | Rename some variables | Dirkjan Ochtman | 2023-09-11 | 1 | -7/+7 |
| | |||||
* | Optimize parsing boolean literals, too | René Kijewski | 2023-08-03 | 1 | -9/+5 |
| | |||||
* | Parse paths and identifiers only once | René Kijewski | 2023-08-03 | 1 | -10/+10 |
| | | | | | | | | | | | | | | In the old implementation each variable in an expression would be parsed up to three times: * Try to parse a path because it contains a leading double colon, or infix double colons. * Try to parse it as path again by scanning for an identifier that contains an upper case character. * Fall back to scanning for any identifier. This PR turns all three steps into one, without the need for backtracking. | ||||
* | parser: don't truncates whitespaces after arrays | René Kijewski | 2023-08-02 | 1 | -1/+1 |
| | |||||
* | Fix parsing arrays | René Kijewski | 2023-07-31 | 1 | -5/+7 |
| | | | | | | | | | | | | | | | | 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 | -3/+5 |
| | | | | | | | This change: * adds a cut when the leading `(` was encountered, and * fixed the interaction between call expressions and boolean OR. | ||||
* | parser: move Expr parser helpers into callers | Dirkjan Ochtman | 2023-07-31 | 1 | -53/+54 |
| | |||||
* | parser: move single expr parsers into Expr impl | Dirkjan Ochtman | 2023-07-31 | 1 | -63/+63 |
| | |||||
* | parser: move binary operator parsers into Expr impl | Dirkjan Ochtman | 2023-07-31 | 1 | -71/+71 |
| | |||||
* | parser: flatten top-level Expr interface | Dirkjan Ochtman | 2023-07-31 | 1 | -35/+27 |
| | |||||
* | parser: move suffix parsers into impl block | Dirkjan Ochtman | 2023-07-31 | 1 | -53/+61 |
| | |||||
* | parser: move nested_parenthesis() helper into node module | Dirkjan Ochtman | 2023-07-31 | 1 | -3/+49 |
| | |||||
* | Extract askama_parser crate | Dirkjan Ochtman | 2023-07-31 | 1 | -0/+285 |