Commit message (Collapse) | Author | Files | Lines | ||
---|---|---|---|---|---|
2024-01-22 | Add ui test for `extends` error | Guillaume Gomez | 2 | -0/+37 | |
2023-11-28 | Add tests for named arguments in macro calls | Guillaume Gomez | 2 | -0/+89 | |
2023-11-20 | Add UI tests for macros error message | Guillaume Gomez | 2 | -0/+50 | |
2023-10-25 | Add UI test for `elif` error message | Guillaume Gomez | 2 | -0/+17 | |
2023-10-25 | Improve error for invalid name used in `endmacro` | Guillaume Gomez | 1 | -1/+2 | |
2023-10-25 | Improve error for invalid name used in `endblock` | Guillaume Gomez | 1 | -1/+2 | |
2023-10-23 | Add test specifically for named blocks, and named macros | Guillaume Gomez | 4 | -0/+32 | |
2023-09-28 | Pass `Node` parsing level to expressions | René Kijewski | 1 | -2/+2 | |
2023-09-28 | Limit nesting in parser nodes, too | René Kijewski | 2 | -0/+129 | |
2023-07-31 | Fix parsing arrays | René Kijewski | 2 | -7/+3 | |
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. | |||||
2023-07-31 | Fix parsing calls | René Kijewski | 1 | -2/+2 | |
This change: * adds a cut when the leading `(` was encountered, and * fixed the interaction between call expressions and boolean OR. | |||||
2023-01-24 | Update `ui` test for trybuild 1.0.76 | René Kijewski | 1 | -1/+1 | |
In <https://github.com/dtolnay/trybuild/pull/219> the output of error messages was subtly changed, because they introduced a subdirectoy in their temp path. This PR fixes the mismatch between the expected and the actual output. | |||||
2022-01-31 | Remove `panic!()` in `loop.cycle([])` | René Kijewski | 2 | -0/+22 | |
2022-01-31 | Make is_shadowing_variable() failable | René Kijewski | 1 | -3/+3 | |
2022-01-31 | Allow comments in `{% match %}` and remove panic! | René Kijewski | 2 | -0/+28 | |
2022-01-13 | Add unit tests if there is one `#[template(…)]` | René Kijewski | 4 | -0/+36 | |
2021-12-01 | Fix tests for new error messages in Rust nightly | René Kijewski | 15 | -1/+27 | |
2021-11-11 | Implement {{loop.cycle(…)}} similar to Jinja | René Kijewski | 2 | -0/+20 | |
2021-08-30 | Ensure that {%break%} is only used inside of a loop | René Kijewski | 2 | -0/+19 | |
2021-07-30 | Better error messages using cuts | René Kijewski | 2 | -0/+19 | |
2021-07-30 | Use "target()" to parse "when" block | René Kijewski | 2 | -0/+18 | |
`target()` as used in parsing "let" and "if let" implements parsing nested tuples and structs. But it does not implement parsing literals. The functions `match_variant()` and `with_parameters()` as used in parsing "when" blocks do not implement parsing nested structs, but it implements parsing literals. This PR combines `match_variant()` and `with_parameters()` into `target()`, so that all `{%when%}` support nested structs, too. | |||||
2021-07-02 | Fix expected error message for missing file | René Kijewski | 4 | -0/+8 | |
rust-lang/rust#82069 made error message that stem macro invocations more verbose. Since Rust 1.54 (currently in beta) the message includes the name of the offending macro. This PR uses version_check to select the appropriate expected error message. | |||||
2020-11-02 | Use `syn::Error::to_compile_error` and add trybuild ui test (#374) | msrd0 | 2 | -0/+15 | |