askama - [no description]

	Commit message (Collapse)	Author	Files	Lines
2022-02-16	Update actix-test requirement from =0.1.0-beta.12 to =0.1.0-beta.13	dependabot[bot]	1	-1/+1
	Updates the requirements on [actix-test](https://github.com/actix/actix-web) to permit the latest version. - [Release notes](https://github.com/actix/actix-web/releases) - [Changelog](https://github.com/actix/actix-web/blob/master/CHANGES.md) - [Commits](https://github.com/actix/actix-web/compare/test-v0.1.0-beta.12...test-v0.1.0-beta.13) --- updated-dependencies: - dependency-name: actix-test dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
2022-02-01	actix: upgrade to actix 4-rc.1	Dirkjan Ochtman	2	-3/+3

2022-01-07	Use Template::MIME_TYPE instead of extension	René Kijewski	1	-7/+4

2022-01-06	Add `#![forbid(unsafe_code)]` to all crates except askama_escape	René Kijewski	1	-0/+1

2022-01-06	Add `#![deny(unreachable_pub)]` to all crates	René Kijewski	1	-0/+1

2022-01-06	No needless boxing of the error	René Kijewski	1	-3/+22

2022-01-06	Combine imports from the same module	René Kijewski	1	-3/+1

2022-01-05	Update for actix-web beta	René Kijewski	3	-25/+22

2022-01-05	Use strict matching for prereleases	Dirkjan Ochtman	1	-4/+5

2022-01-04	askama_actix: revert to actix-web v3 for release	Dirkjan Ochtman	3	-14/+13

2021-12-15	Use a separate trait for object safety (#579)	Dirkjan Ochtman	1	-3/+2
	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-14	updated for actix-web 4.0.0-beta.14	CrunkLord420	1	-2/+2

2021-12-01	Add missing license files to askama_actix and askama_mendes	René Kijewski	2	-0/+2

2021-11-24	Bump version numbers	Dirkjan Ochtman	1	-1/+1

2021-11-24	Remove authors from Cargo metadata (see RFC 3052)	Dirkjan Ochtman	1	-1/+0

2021-11-11	Prepare for actix-web v4 (#553)	Sergey Pashinin	3	-14/+15

2021-08-21	Bump version numbers in anticipation of beta release	Dirkjan Ochtman	1	-1/+1

2021-07-01	Stop eliding lifetimes in paths	Dirkjan Ochtman	1	-0/+2

2021-02-15	Rename askama_actix trait method as suggested by clippy	Dirkjan Ochtman	3	-7/+7
	By bumping the dependency versions for askama and askama_shared, this should be safe.
2020-12-21	Disable askama's default features in web framework crates	Randati	1	-1/+1
	Without disabling these default features, askama's default features get automatically enabled when web framework specific crates are included in the project.
2020-10-18	askama_actix: bump version to 0.11.1	Dirkjan Ochtman	1	-1/+1

2020-09-25	Do not include default actix-web features	Rob Ede	1	-1/+1
	closes #360
2020-09-11	actix: upgrade to actix 3	Dirkjan Ochtman	1	-2/+2

2020-06-30	Tweak dependency on futures for Actix integration	Dirkjan Ochtman	2	-1/+8

2020-06-30	Reference READMEs in crate metadata	Dirkjan Ochtman	1	-0/+1

2020-06-30	Add README files for subcrates	Dirkjan Ochtman	1	-0/+9

2020-06-30	Bump version numbers	Dirkjan Ochtman	1	-2/+2

2020-02-08	Adapt to new warnings and formatting	Dirkjan Ochtman	1	-5/+3

2020-01-29	Move Actix-Web integration into separate askama_actix crate	Dirkjan Ochtman	4	-0/+98