aboutsummaryrefslogtreecommitdiffstats
path: root/testing/tests/ui (unfollow)
Commit message (Collapse)AuthorFilesLines
2024-01-22Add ui test for `extends` errorLibravatar Guillaume Gomez2-0/+37
2023-11-28Add tests for named arguments in macro callsLibravatar Guillaume Gomez2-0/+89
2023-11-20Add UI tests for macros error messageLibravatar Guillaume Gomez2-0/+50
2023-10-25Add UI test for `elif` error messageLibravatar Guillaume Gomez2-0/+17
2023-10-25 Improve error for invalid name used in `endmacro`Libravatar Guillaume Gomez1-1/+2
2023-10-25Improve error for invalid name used in `endblock`Libravatar Guillaume Gomez1-1/+2
2023-10-23Add test specifically for named blocks, and named macrosLibravatar Guillaume Gomez4-0/+32
2023-09-28Pass `Node` parsing level to expressionsLibravatar René Kijewski1-2/+2
2023-09-28Limit nesting in parser nodes, tooLibravatar René Kijewski2-0/+129
2023-07-31 Fix parsing arraysLibravatar René Kijewski2-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 callsLibravatar René Kijewski1-2/+2
This change: * adds a cut when the leading `(` was encountered, and * fixed the interaction between call expressions and boolean OR.
2023-01-24Update `ui` test for trybuild 1.0.76Libravatar René Kijewski1-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-31Remove `panic!()` in `loop.cycle([])`Libravatar René Kijewski2-0/+22
2022-01-31Make is_shadowing_variable() failableLibravatar René Kijewski1-3/+3
2022-01-31Allow comments in `{% match %}` and remove panic!Libravatar René Kijewski2-0/+28
2022-01-13Add unit tests if there is one `#[template(…)]`Libravatar René Kijewski4-0/+36
2021-12-01Fix tests for new error messages in Rust nightlyLibravatar René Kijewski15-1/+27
2021-11-11Implement {{loop.cycle(…)}} similar to JinjaLibravatar René Kijewski2-0/+20
2021-08-30Ensure that {%break%} is only used inside of a loopLibravatar René Kijewski2-0/+19
2021-07-30Better error messages using cutsLibravatar René Kijewski2-0/+19
2021-07-30Use "target()" to parse "when" blockLibravatar René Kijewski2-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-02Fix expected error message for missing fileLibravatar René Kijewski4-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-02Use `syn::Error::to_compile_error` and add trybuild ui test (#374)Libravatar msrd02-0/+15