Tide v0.13.0 Release Notes

Release Date: 2020-07-31 // about 2 years ago
  • ๐Ÿ“„ Docs

    ๐Ÿš€ This release introduces first-class support for sessions, fixes a
    0๏ธโƒฃ long-standing bug with our default middleware, clarifies our stability
    guarantees, and renamed the API to register middleware through.


    ๐Ÿ‘ We're excited to announce initial support for sessions in Tide. This feature
    enables Tide applications to associate multiple separate requests as
    ๐Ÿ— belonging to the same origin. Which is a pre-requisite to build common
    ๐ŸŒ web-app features such as user accounts, multi-request transactions, and

    ๐Ÿ— Tide sessions are generic over backend stores and signing strategy. It builds
    ๐Ÿš€ on the newly released async-session
    ๐Ÿ“„ 2.0.0
    library, which is a set of common
    traits that types that make up a session. But beyond that, much of it is
    implementation specific.

    0๏ธโƒฃ Tide ships with a memory and cookie store by default. However we have
    also published several convenient session store implementations for common
    databases, providing a nice selection to choose from:

    Using "Redis" as the backing session store for Tide is as easy as writing 3
    lines and including a dependency in your Cargo.toml:

    use async\_redis\_session::RedisSessionStore;use tide::sessions::SessionMiddleware;use tide::{Redirect, Request}; #[async\_std::main]async fn main() -\> tide::Result\<()\> { let mut app = tide::new(); // Create a Redis-backed session store and use it in the applet store = RedisSessionStore::new("redis://")?; let secret = std::env::var("SESSION\_SECRET").unwrap(); app.with(SessionMiddleware::new(store, secret.as\_bytes())); app.at("/").get(|mut req: Request\<()\>| async move { // Store a counter in the session; increment it by one on each visitlet session = req.session\_mut(); let visits: usize = session.get("visits").unwrap\_or\_default(); session.insert("visits", visits + 1).unwrap(); // Render a page that shows the number of requests made in the sessionlet visits: usize = req.session().get("visits").unwrap(); Ok(format!("you have visited this website {} times", visits)) }); // Close the current session app.at("/reset").get(|mut req: Request\<()\>| async move { req.session\_mut().destroy(); Ok(Redirect::new("/")) }); // Start the server app.listen("").await?; Ok(()) }

    It's still early for Tide sessions. But we're incredibly excited for how
    convenient it already is, and excited for the possibilities this will enable!

    Renaming Server::middleware to Server::with

    This patch renames Server::middleware to Server::with in order to
    streamline much of the middleware APIs.

    // After this patchlet mut app = tide::new(); app.with(MyMiddleware::new()); app.at("/").get(|\_| async move { Ok("hello chashu") }); app.listen("localhost:8080").await?;// Before this patchlet mut app = tide::new(); app.middleware(MyMiddleware::new()); app.at("/").get(|\_| async move { Ok("hello chashu") }); app.listen("localhost:8080").await?;

    A small change, but ever so convenient.

    ๐ŸŒฒ No more duplicate log messages

    0๏ธโƒฃ Ever since we introduced application nesting we've had issues with default
    ๐Ÿ›  middleware running twice. This patch fixes that for our logging middleware in
    two ways:

    0๏ธโƒฃ 1. We've introduced a logger Cargo feature to disable the default logging middleware #661

    1. We now track calls to the logger inside the state map to ensure
      it's only called once per app #662

    โšก๏ธ There may be room to optimize this further in the future, and perhaps extend
    the same mechanisms to work for more built-in middleware. But for now this
    patch resolves the most common issues people were reporting.

    Clarification on stability

    ๐Ÿš€ Tide has been deployed to production in many places: independent authors
    ๐Ÿ— taking control of their publishing pipelines, software professionals building
    internal tooling, and enterprises running it in key parts of their

    ๐Ÿš€ In past Tide releases shipped with a warning that actively recommended
    ๐Ÿš‘ against using it in any critical path. However we've chosen to no longer
    ๐Ÿš€ include that warning starting this release. Much of the work at the protocol
    layer and below has completed, and we've received positive reports on how it

    For the foreseable future Tide will remain on the 0.x.x semver range. While
    we're confident in our foundations, we want to keep iterating on the API.
    ๐Ÿš€ Once we find that work has slowed down we may decide when to release a 1.0.0
    ๐Ÿš€ release.

    โž• Added

    • โž• Added From<StatusCode> for Response #650
    • โž• Added a feature-flag to disable the default logger middleware #661
    • โž• Added impl Into<Request> for http_types::Request #670

    ๐Ÿ”„ Changes

    • ๐Ÿ“‡ Rename Server::middleware to Server::with #666
    • โฌ†๏ธ Relax Sync bound on Fut required on sse::upgrade #647
    • Consistency improvements for examples #651
    • โฌ†๏ธ Bumped version number in docs #652
    • โž• Add enable logging in README example #657
    • โœ‚ Remove "experimental" warning #667

    ๐Ÿ›  Fixes

    • ๐ŸŒฒ Guarantee the log middleware is only run once per request #662


    • โœ… Enable clippy for tests #655
    • Reorder deps in cargo.toml #658