aboutsummaryrefslogtreecommitdiffstats
path: root/testing/tests (follow)
Commit message (Collapse)AuthorAgeFilesLines
* Pass `Node` parsing level to expressionsLibravatar René Kijewski2023-09-281-2/+2
|
* Limit nesting in parser nodes, tooLibravatar René Kijewski2023-09-282-0/+129
|
* Fix parsing arraysLibravatar René Kijewski2023-07-312-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.
* Fix parsing callsLibravatar René Kijewski2023-07-311-2/+2
| | | | | | | This change: * adds a cut when the leading `(` was encountered, and * fixed the interaction between call expressions and boolean OR.
* Fix Rust macro invocations not accepting a path (#837)Libravatar Matthew Taylor2023-07-241-2/+22
|
* Allow macros to be defined and called without argumentsLibravatar mataha2023-06-121-0/+10
| | | | | | | | | | This commit introduces a shorthand for defining and calling macros when using them as a reusable substitute for variables assigned complex values (e.g. string literals with or without newline escapes). The use-case is formatting - from my experience it's easier to visually parse a `macro` `endmacro` block than a multiline variable assignment. Signed-off-by: mataha <mataha@users.noreply.github.com>
* Add tests for whitespace argument in template derive proc-macroLibravatar Guillaume Gomez2023-03-131-0/+24
|
* Update tests for whitespace characters handlingLibravatar Guillaume Gomez2023-03-093-437/+471
|
* Propogate size_hint from sub-blocks (#788)Libravatar Andrew Dona-Couch -- GitHub drop ICE2023-03-061-0/+47
| | | Closes #786
* Apply clippy suggestions for 1.67 (#769)Libravatar Dirkjan Ochtman2023-01-302-5/+4
|
* Update `ui` test for trybuild 1.0.76Libravatar René Kijewski2023-01-241-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.
* chore: remove allow(clippy::disallowed_names)Libravatar Dirkjan Ochtman2022-11-074-7/+1
|
* chore: apply clippy suggestions for 1.65Libravatar Dirkjan Ochtman2022-11-074-4/+4
|
* Remove support for deprecated `_parent` fieldLibravatar René Kijewski2022-07-251-4/+40
| | | | | | The support for the magic `_parent` field is deprecated since v0.8.0 or issue #180. It's bothersome to keep this feature alive, when no-one should be using it for 3 years.
* Allow `{% endmacro name %}`Libravatar Bastien Orivel2022-04-291-1/+1
| | | | | | Just migrated a repo from tera to askama and this was one of the only things that was different. This is also coherent with `{% block %}` for which I added the same feature years ago.
* Add test for "minimize" configLibravatar Guillaume Gomez2022-04-261-0/+43
|
* Add test for suppress_whitespace optionLibravatar Guillaume Gomez2022-04-212-19/+340
|
* Make json filter safeLibravatar René Kijewski2022-02-162-1/+63
| | | | | | | | | | | | | | | | | | | | | Previously the built-in json filter had an issue that made it unsafe to use in HTML data. When used in HTML attributes an attacker who is able to supply an arbitrary string that should be JSON encoded could close the containing HTML element e.g. with `"</div>"`, and write arbitrary HTML code afterwards as long as they use apostrophes instead of quotation marks. The programmer could make this use case safe by explicitly escaping the JSON result: `{{data|json|escape}}`. In a `<script>` context the json filter was not usable at all, because in scripts HTML escaped entities are not parsed outside of XHTML documents. Without using the safe filter an attacker could close the current script using `"</script>"`. This PR fixes the problem by always escaping less-than, greater-than, ampersand, and apostrophe characters using their JSON unicode escape sequence `\u00xx`. Unless the programmer explicitly uses the safe filter, quotation marks are HTML encoded as `&quot`. In scripts the programmer should use the safe filter, otherwise not.
* Add markdown filterLibravatar René Kijewski2022-02-071-0/+75
|
* Remove `panic!()` in `loop.cycle([])`Libravatar René Kijewski2022-01-312-0/+22
|
* Make is_shadowing_variable() failableLibravatar René Kijewski2022-01-311-3/+3
|
* Allow comments in `{% match %}` and remove panic!Libravatar René Kijewski2022-01-313-0/+53
|
* Parse tuple expressionsLibravatar René Kijewski2022-01-281-0/+82
| | | | | | | Askama understands how to destructure tuples in let and match statements, but it does not understand how to build a tuple. This PR fixes this shortcoming.
* Implement error propagation expression: `?` (#590)Libravatar René Kijewski2022-01-281-0/+69
| | | | | | This change allows using the operator `?` in askama expressions. It works like the same operator in Rust: if a `Result` is `Ok`, it is unwrapped. If it is an error, then the `render()` method fails with this error value.
* Unify handling of calls (#614)Libravatar René Kijewski2022-01-271-0/+82
| | | | | Instead of having `Expr::VarCall`, `Expr::PathCall` and `Expr::MethodCall`, this PR unifies the handling of calls by removing the former three variants, and introducing `Expr::Call`.
* Add unit tests if there is one `#[template(…)]`Libravatar René Kijewski2022-01-134-0/+36
|
* Use a separate trait for object safety (#579)Libravatar Dirkjan Ochtman2021-12-152-11/+8
| | | | | | | | | | | | | | | | | | This is relatively major change to the main trait's API. For context, I always started from the concept of monomorphized traits, but later several contributors asked about object safety. At that point I made `Template` object-safe, and then even later added a `SizedTemplate` to make some things easier for people who don't need object safety. However, having object-safety in the primary trait is bad for performance (a substantial number of calls into the virtual `Write` trait is relatively slow), and I don't think those who don't need object safety should pay for the cost of having it. Additionally, I feel using associated consts for the extension and size hint is more idiomatic than having accessor methods. I don't know why I didn't use these from the start -- maybe associated consts didn't exist yet, or I didn't yet know how/when to use them. Askama is pretty old at this point...
* Fix tests for new error messages in Rust nightlyLibravatar René Kijewski2021-12-0116-5/+41
|
* Allow whitespace trimming in {{raw}} blocksLibravatar René Kijewski2021-11-291-0/+10
|
* Added optional escaper testsLibravatar vallentin2021-11-191-0/+48
|
* Implement `for … in … if …`Libravatar René Kijewski2021-11-111-0/+18
|
* Add exhaustive whitespace tests for for-elseLibravatar René Kijewski2021-11-112-0/+1147
|
* Implement for-elseLibravatar René Kijewski2021-11-111-0/+19
| | | | | | | | | | | | | This PR implements for-else statements like in Jinja. They make it easy to print an alternative message if the loop iterator was empty. E.g. ```rs {% for result in result %} <li>{{ result }}</li> {% else %} <li><em>no results</em></li> {% endfor %} ```
* Implement {{loop.cycle(…)}} similar to JinjaLibravatar René Kijewski2021-11-113-0/+65
|
* Make test name consistent with test template nameLibravatar Kelly Thomas Kline2021-10-131-1/+1
|
* Initial test workLibravatar Kelly Thomas Kline2021-10-131-0/+16
|
* Ensure that {%break%} is only used inside of a loopLibravatar René Kijewski2021-08-302-0/+19
|
* Add {% break %} and {% continue %}Libravatar René Kijewski2021-08-301-0/+68
| | | | | This PR adds `{% break %}` and `{% continue %}` statements to break out of a loop, or continue with the next element of the iterator.
* Add test case for matching on Option<bool>Libravatar Restioson2021-08-251-0/+18
|
* Issue #379 was fixedLibravatar René Kijewski2021-07-301-0/+10
| | | | | | | | This PR adds the tests by @msrd0 <git@msrd0.de> that failed before. The error was fixed somewhen between f23162a and now, so these tests serve to prevent regressions in the future. I simplified the tests very slightly to omit whitespaces in the output.
* Better error messages using cutsLibravatar René Kijewski2021-07-302-0/+19
|
* Use "target()" to parse "when" blockLibravatar René Kijewski2021-07-304-0/+68
| | | | | | | | | | | | `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.
* Allow omitting "with" keyword in match blocksLibravatar René Kijewski2021-07-301-0/+17
| | | | | | | | | Askama uses the syntax `{% when Variant with (parameters) %}` in `{% match %}` blocks. This is done because Askama does not implement the whole pattern matching of Rust's `match` statements. This PR wants to bring Askama a step closer Rust's matching, so the "with" keyword should not be needed anymore.
* Allow using "with" keyword in "let" statementsLibravatar René Kijewski2021-07-301-0/+14
| | | | | | | | Askama uses the syntax `{% when Variant with (parameters) %}` in `{% match %}` blocks. This change allows the optional use of the keyword "with" in "let" and "if let" statements, too.
* Implement destructoring of structsLibravatar René Kijewski2021-07-051-0/+107
| | | | | This PR implements the destructoring of structs on the lhs of "let" and "for" statements.
* Add "destructoring tuple in loop" testLibravatar René Kijewski2021-07-051-0/+69
|
* Add tuple destructoring testsLibravatar René Kijewski2021-07-051-0/+14
|
* Add loop variable shadowing testLibravatar René Kijewski2021-07-051-0/+21
|
* Replace rust_macro test to work on nightlyLibravatar René Kijewski2021-07-021-11/+15
| | | | | | | | | | | | | | | | The current rust_test uses `stringify!()`. The documentation gives us the warning: > Note that the expanded results of the input tokens may change in the > future. You should be careful if you rely on the output. In the current nightly rust the result was indeed changed, so the test not fails. This PR replaces the test with another macro, that does not depend on `stringify!()`. Closes issue #504.
* Fix expected error message for missing fileLibravatar René Kijewski2021-07-025-0/+15
| | | | | | | | | 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.
generated by cgit (git 2.34.1) at 2024-11-22 06:02:26 +0000