Rob Ede
Rob Ede
It would be okay to take inspiration from that feature, but we are not able to update the `cookie` crate to 0.17 without a major version bump. Though if that...
The `actix` crate is in maintenance mode, which is to say no one on the team has an interest in developing features for it any more. I welcome forks of...
FWIW, as of now, the `chrono` crate has been picked up by reliable maintainers. I'm not convinced that switching out its use in Tera would have any advantages at all.
Exactly. Our use case uses the Input and Output types in a trait interface that abstracts over in-memory, disk, and S3 "backends" but always trying to respect S3 parameter semantics....
Almost. Would be enough if there was either: - a way to convert an Input back into an InputBuilder - a similar `Input::send_with()` In general this just seems like a...
Luckily, I have control of the interface so I decided to change everything to `*InputBuilder`s which does solve my specific issue since I now have access to `send_with()`.
It seems to me that setting one level to apply to all compression formats is not a good enough solution. We'd need a compression level setting per encoding.
I'd be interested to merge this if we can fix the CI.
the right place for community crates is in the actix-extras readme: https://github.com/actix/actix-extras#community-crates
migrated to https://github.com/dalek-cryptography/curve25519-dalek/pull/542