aboutsummaryrefslogtreecommitdiffstats
path: root/testing (unfollow)
Commit message (Collapse)AuthorFilesLines
2023-05-24Update criterion requirement from 0.4 to 0.5Libravatar dependabot[bot]1-1/+1
Updates the requirements on [criterion](https://github.com/bheisler/criterion.rs) to permit the latest version. - [Changelog](https://github.com/bheisler/criterion.rs/blob/master/CHANGELOG.md) - [Commits](https://github.com/bheisler/criterion.rs/compare/0.4.0...0.5.0) --- updated-dependencies: - dependency-name: criterion dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
2023-05-20Upgrade to comrak 0.18Libravatar Dirkjan Ochtman1-1/+1
2023-03-28Update comrak to 0.17Libravatar Dirkjan Ochtman1-1/+1
2023-03-13Add tests for whitespace argument in template derive proc-macroLibravatar Guillaume Gomez1-0/+24
2023-03-09Update tests for whitespace characters handlingLibravatar Guillaume Gomez3-437/+471
2023-03-06Propogate size_hint from sub-blocks (#788)Libravatar Andrew Dona-Couch -- GitHub drop ICE4-0/+52
Closes #786
2023-03-03Bump versions for Askama 0.12 (#784)Libravatar Dirkjan Ochtman1-1/+1
2023-01-30Update comrak dependency to 0.16Libravatar René Kijewski1-1/+1
2023-01-30Apply clippy suggestions for 1.67 (#769)Libravatar Dirkjan Ochtman3-6/+6
2023-01-24Update `ui` test for trybuild 1.0.76Libravatar René Kijewski2-2/+2
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-11-15Update comrak requirement from 0.14 to 0.15Libravatar dependabot[bot]1-1/+1
Updates the requirements on [comrak](https://github.com/kivikakk/comrak) to permit the latest version. - [Release notes](https://github.com/kivikakk/comrak/releases) - [Changelog](https://github.com/kivikakk/comrak/blob/main/changelog.txt) - [Commits](https://github.com/kivikakk/comrak/compare/0.14.0...0.15.0) --- updated-dependencies: - dependency-name: comrak dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
2022-11-07chore: remove allow(clippy::disallowed_names)Libravatar Dirkjan Ochtman4-7/+1
2022-11-07chore: apply clippy suggestions for 1.65Libravatar Dirkjan Ochtman4-4/+4
2022-10-21Version bump in README and bookLibravatar Allan Zhang1-1/+1
I was going through the book when I saw the version was still 0.8. This commit ensures all references to Askama version are to 0.11.2. Most of them already were. Merge whenever appropriate for release, #722 related
2022-09-26Update criterion requirement from 0.3 to 0.4 (#721)Libravatar dependabot[bot]1-1/+1
Updates the requirements on [criterion](https://github.com/bheisler/criterion.rs) to permit the latest version. - [Release notes](https://github.com/bheisler/criterion.rs/releases) - [Changelog](https://github.com/bheisler/criterion.rs/blob/master/CHANGELOG.md) - [Commits](https://github.com/bheisler/criterion.rs/compare/0.3.0...0.4.0) --- updated-dependencies: - dependency-name: criterion dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2022-07-25Remove support for deprecated `_parent` fieldLibravatar René Kijewski1-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.
2022-07-20Update to comrak v0.14Libravatar René Kijewski1-1/+1
2022-06-07Update comrak requirement from 0.12 to 0.13Libravatar dependabot[bot]1-1/+1
Updates the requirements on [comrak](https://github.com/kivikakk/comrak) to permit the latest version. - [Release notes](https://github.com/kivikakk/comrak/releases) - [Changelog](https://github.com/kivikakk/comrak/blob/main/changelog.txt) - [Commits](https://github.com/kivikakk/comrak/compare/0.12.0...0.13.0) --- updated-dependencies: - dependency-name: comrak dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
2022-04-29Allow `{% endmacro name %}`Libravatar Bastien Orivel2-1/+13
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.
2022-04-26Add test for "minimize" configLibravatar Guillaume Gomez2-0/+45
2022-04-21Rename `suppress_whitespace` into `whitespace` and update expected values to ↵Libravatar Guillaume Gomez1-1/+1
"suppress" and "preserve"
2022-04-21Add test for suppress_whitespace optionLibravatar Guillaume Gomez3-19/+342
2022-02-16Make json filter safeLibravatar René Kijewski3-2/+64
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.
2022-02-07Add markdown filterLibravatar René Kijewski2-1/+79
2022-01-31Use exact trybuild versionLibravatar René Kijewski1-1/+1
Sometimes for no obvious reason an old version is selected and the output is different in just about every ui test. Just pin it to the currently newest version and test if an updated version still works when a new version gets released.
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é Kijewski3-0/+53
2022-01-28Parse tuple expressionsLibravatar René Kijewski1-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.
2022-01-28 Implement error propagation expression: `?` (#590)Libravatar René Kijewski1-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.
2022-01-27Unify handling of calls (#614)Libravatar René Kijewski1-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`.
2022-01-13Add unit tests if there is one `#[template(…)]`Libravatar René Kijewski4-0/+36
2021-12-15Use a separate trait for object safety (#579)Libravatar Dirkjan Ochtman2-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...
2021-12-01Fix tests for new error messages in Rust nightlyLibravatar René Kijewski16-5/+41
2021-11-29Allow whitespace trimming in {{raw}} blocksLibravatar René Kijewski2-0/+12
2021-11-19Added optional escaper testsLibravatar vallentin1-0/+48
2021-11-11Implement `for … in … if …`Libravatar René Kijewski1-0/+18
2021-11-11Add exhaustive whitespace tests for for-elseLibravatar René Kijewski2-0/+1147
2021-11-11Implement for-elseLibravatar René Kijewski1-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 %} ```
2021-11-11Implement {{loop.cycle(…)}} similar to JinjaLibravatar René Kijewski3-0/+65
2021-10-13Make test name consistent with test template nameLibravatar Kelly Thomas Kline1-1/+1
2021-10-13Initial test workLibravatar Kelly Thomas Kline1-0/+16
2021-08-30Ensure that {%break%} is only used inside of a loopLibravatar René Kijewski2-0/+19
2021-08-30Add {% break %} and {% continue %}Libravatar René Kijewski2-0/+79
This PR adds `{% break %}` and `{% continue %}` statements to break out of a loop, or continue with the next element of the iterator.
2021-08-25Add test case for matching on Option<bool>Libravatar Restioson2-0/+26
2021-08-21Bump version numbers in anticipation of beta releaseLibravatar Dirkjan Ochtman1-1/+1
2021-07-30Issue #379 was fixedLibravatar René Kijewski3-0/+38
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.
2021-07-30Better error messages using cutsLibravatar René Kijewski2-0/+19
2021-07-30Use "target()" to parse "when" blockLibravatar René Kijewski5-0/+78
`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-30Allow omitting "with" keyword in match blocksLibravatar René Kijewski1-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.
generated by cgit (git 2.34.1) at 2024-11-23 12:29:49 +0000