aboutsummaryrefslogtreecommitdiffstats
path: root/askama_shared (follow)
Commit message (Collapse)AuthorAgeFilesLines
* Rename `suppress_whitespace` into `whitespace` and update expected values to ↵Libravatar Guillaume Gomez2022-04-212-19/+55
| | | | "suppress" and "preserve"
* Add config option to derive macro so we can specify config file locationLibravatar Guillaume Gomez2022-04-213-3/+17
|
* Parse template derive args outside of TemplateInput::newLibravatar Guillaume Gomez2022-04-212-98/+125
|
* Update parser to allow "+" signLibravatar Guillaume Gomez2022-04-212-166/+218
|
* Add suppress_whitespace config optionLibravatar Guillaume Gomez2022-04-213-7/+49
|
* Simplify the implementation of askama_axumLibravatar Jonas Platte2022-03-311-1/+1
|
* Add io::writer helper methodsLibravatar René Kijewski2022-03-311-2/+20
| | | | | | It might not be immediately obvious to everyone how easy it is to use Askama template with std::io (e.g. files) instead of std::fmt, so this PR adds a few helper methods to make this more obvious to novice users.
* Expose the fact that templates implement DisplayLibravatar René Kijewski2022-03-311-2/+21
| | | | | This is a quite useful feature, because you can use templates in format!(), format_args!(), etc.
* Move Template into askama_shared, tooLibravatar René Kijewski2022-03-301-0/+88
| | | | | | The traits Template and DynTemplate need to be in sync with askama_shared's generator. #647 consolidated the template crating into askama_shared, this PR moves the trait itself.
* Implement std::error::Error::sourceLibravatar René Kijewski2022-03-281-4/+4
| | | | Error::cause() is deprecated since Rust 1.33.
* fix formattingLibravatar Axel Kappel2022-03-261-1/+1
|
* made capitalize filter unicode awareLibravatar Axel Kappel2022-03-261-13/+10
|
* Merge derive.rs into generator.rsLibravatar René Kijewski2022-03-233-119/+100
|
* Update version numbersLibravatar René Kijewski2022-03-231-1/+1
|
* Un-"pub" most of askama_shared's internalsLibravatar René Kijewski2022-03-236-81/+81
| | | | | Previously askama_shared exported most of it's internals, so askama_derive could use them. This is not needed anymore.
* Reduce askama_derive to a single re-exportLibravatar René Kijewski2022-03-232-0/+107
| | | | | | | | | | All the hard work in askama_derive was actually done in askama_shared. This PR removes the back-and-forth interaction between the two crates. Now askama_derive is a single re-export of `#[derive(Template)]` which has to be done in a proc_macro crate. This most likely means that askama_derive is "final", unless another derive template needs to be introduced in the future.
* Move handling of integrations into askama_sharedLibravatar René Kijewski2022-03-233-50/+35
| | | | | | | Before this PR the handling of integrations was done both by askama_shared and askama_derive. This diff lets askama_shared do the work. This will prevent problems like #629, when both packages might come out of sync.
* Fix clippy warningLibravatar René Kijewski2022-03-231-1/+1
|
* Actix Web v4.0 is hereLibravatar René Kijewski2022-02-252-5/+5
|
* Increment patch versions of askama_{shared,escape}Libravatar René Kijewski2022-02-161-1/+1
|
* Make json filter safeLibravatar René Kijewski2022-02-163-18/+25
| | | | | | | | | | | | | | | | | | | | | 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.
* askama_mendes: upgrade mendes to 0.0.62 (#636)Libravatar Dirkjan Ochtman2022-02-091-1/+1
|
* Add markdown filterLibravatar René Kijewski2022-02-073-3/+96
|
* Enable tracking of the offending span of an errorLibravatar René Kijewski2022-02-071-5/+24
|
* 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-033-47/+42
|
* Remove used optional dependencyLibravatar René Kijewski2022-01-311-1/+0
|
* Remove `panic!()` in `loop.cycle([])`Libravatar René Kijewski2022-01-311-1/+1
|
* 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-311-12/+24
|
* Allow comments in `{% match %}` and remove panic!Libravatar René Kijewski2022-01-311-19/+2
|
* Parse tuple expressionsLibravatar René Kijewski2022-01-282-3/+163
| | | | | | | 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-283-6/+30
| | | | | | 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-272-145/+157
| | | | | 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-242-9/+9
| | | | | PathBuf is to String like Path is to str, so `&PathBuf` is a pointer to a pointer. Clippy does not likes that.
* Tweak attribute parsing some moreLibravatar Dirkjan Ochtman2022-01-131-10/+7
|
* 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
|
* 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-121-3/+3
|
* Fully qualify some more paths in generated codeLibravatar René Kijewski2022-01-121-3/+3
|
* Determine Content-Type during compilationLibravatar René Kijewski2022-01-072-0/+10
|
* 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-073-0/+30
|
* 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-062-27/+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.
generated by cgit (git 2.34.1) at 2024-11-22 06:43:54 +0000