aboutsummaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* Take reference to AST ident only onceLibravatar René Kijewski2022-02-031-12/+17
|
* Replace if-let with matchLibravatar René Kijewski2022-02-031-4/+6
|
* Replace custom Cow with actual CowLibravatar René Kijewski2022-02-034-49/+45
|
* Update README.md, sync with the bookLibravatar René Kijewski2022-02-022-3/+4
|
* actix: upgrade to actix 4-rc.1Libravatar Dirkjan Ochtman2022-02-012-3/+3
|
* Use exact trybuild versionLibravatar René Kijewski2022-01-311-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.
* Remove used optional dependencyLibravatar René Kijewski2022-01-311-1/+0
|
* Remove `panic!()` in `loop.cycle([])`Libravatar René Kijewski2022-01-313-1/+23
|
* Don't wrap in StrLit just to extract the str imm.Libravatar René Kijewski2022-01-311-20/+4
|
* Update comment in TemplateInput::new()Libravatar René Kijewski2022-01-311-1/+1
|
* Make is_shadowing_variable() failableLibravatar René Kijewski2022-01-312-15/+27
|
* Allow comments in `{% match %}` and remove panic!Libravatar René Kijewski2022-01-314-19/+55
|
* Parse tuple expressionsLibravatar René Kijewski2022-01-283-3/+245
| | | | | | | 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-284-6/+99
| | | | | | 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-273-145/+239
| | | | | 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`.
* Replace `&PathBuf` with `&Path`Libravatar René Kijewski2022-01-243-12/+12
| | | | | PathBuf is to String like Path is to str, so `&PathBuf` is a pointer to a pointer. Clippy does not likes that.
* Fix json/yaml featuresLibravatar Jannik Obermann2022-01-152-2/+4
|
* Tweak attribute parsing some moreLibravatar Dirkjan Ochtman2022-01-131-10/+7
|
* Add unit tests if there is one `#[template(…)]`Libravatar René Kijewski2022-01-134-0/+36
|
* Make sure '#[template(…)]' is given exactly onceLibravatar René Kijewski2022-01-131-16/+22
|
* Rename "meta" in proc_macro parserLibravatar René Kijewski2022-01-131-3/+3
|
* README: Adds link to JinjaLibravatar hoijui2022-01-131-1/+1
| | | ... for those of us who do not know what it is.
* Add template argument for contexts' hasherLibravatar René Kijewski2022-01-121-2/+2
| | | | | In askama_shared::generate a custom hasher for the contexts can be given, so Heritage needs to accept the argument to.
* `&Option<T>` → `Option<&T>`Libravatar René Kijewski2022-01-122-4/+4
|
* Fully qualify some more paths in generated codeLibravatar René Kijewski2022-01-121-3/+3
|
* Use Template::MIME_TYPE instead of extensionLibravatar René Kijewski2022-01-078-43/+25
|
* Determine Content-Type during compilationLibravatar René Kijewski2022-01-073-0/+22
|
* Make TemplateInput::extension() reusableLibravatar René Kijewski2022-01-071-1/+7
|
* Unshadow function escaping()Libravatar René Kijewski2022-01-071-3/+3
|
* Move extension_to_mime_type() to askama_sharedLibravatar René Kijewski2022-01-075-27/+37
|
* Optimize parsing of rangesLibravatar René Kijewski2022-01-061-17/+13
| | | | | | | | | | Right now almost every expression needs to be parsed twice: `expr_any()` first parses the left-hand side of a range expression, and if no `..` or `..=` was found the left-hand expression is parsed again, this time as the result of the function. This diff removes the second parsing step by first looking for `.. (opt rhs)`, then for `lhs .. (opt rhs)`.
* Add `#[inline]` to trivial trait implementationsLibravatar René Kijewski2022-01-061-0/+9
|
* Remove the iron integration from generatorLibravatar René Kijewski2022-01-065-30/+0
| | | | | | | Issue #527 removed the askama_iron package, but not the integration if someone uses askama_derive's feature with "iron". The old askama_iron crate uses askama v0.10, so it will still work.
* Add `#![forbid(unsafe_code)]` to all crates except askama_escapeLibravatar René Kijewski2022-01-0610-0/+10
|
* Add `#![deny(unreachable_pub)]` to all cratesLibravatar René Kijewski2022-01-0611-0/+11
|
* No needless boxing of the errorLibravatar René Kijewski2022-01-061-3/+22
|
* Omit implicit lifetimesLibravatar René Kijewski2022-01-065-9/+9
|
* Add `#[derive(Debug)]` for public typesLibravatar René Kijewski2022-01-061-0/+3
|
* Same number of repeats in macro pattern and bodyLibravatar René Kijewski2022-01-061-1/+1
|
* No need to build a String when it gets referenced as &str implicitlyLibravatar René Kijewski2022-01-061-6/+0
|
* Combine imports from the same moduleLibravatar René Kijewski2022-01-062-5/+2
|
* Remove unused importsLibravatar René Kijewski2022-01-061-7/+0
|
* Update for actix-web betaLibravatar René Kijewski2022-01-054-32/+25
|
* Use strict matching for prereleasesLibravatar Dirkjan Ochtman2022-01-051-4/+5
|
* Bump version number for askama_sharedLibravatar Dirkjan Ochtman2022-01-041-1/+1
|
* askama_rocket: revert to rocket 0.4 for releaseLibravatar Dirkjan Ochtman2022-01-044-10/+14
|
* askama_actix: revert to actix-web v3 for releaseLibravatar Dirkjan Ochtman2022-01-044-17/+17
|
* askama_axum: prepare version 0.1.0Libravatar Dirkjan Ochtman2022-01-041-2/+2
|
* Fix suggestions from nightly clippyLibravatar Dirkjan Ochtman2021-12-221-0/+1
|
* Use a separate trait for object safety (#579)Libravatar Dirkjan Ochtman2021-12-155-39/+84
| | | | | | | | | | | | | | | | | | 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...
generated by cgit (git 2.34.1) at 2025-02-17 01:39:35 +0000