Path: make content field pub again

[abonander]

PR Type

Refactor

PR Checklist

• Tests for the changes have been added / updated.
• Documentation comments have been added / updated.
• A changelog entry has been made for the appropriate packages.
• Format code with the latest stable rustfmt.
• (Team) Label with affected crates and semver status.

Overview

Upgrading to the beta and this seems to have changed from 3.3.5 but no reason is given in #1894 for the change. The content field of Json is still public which confuses me as to why Path and Query got this treatment but Json did not.

I recently switched from calling .into_inner() to destructuring in the function arguments and it's a lot nicer, especially for singular path arguments such as:

#[get("/user/{id}")]
async fn get_user(Path(user_id): Path<Uuid>) -> Option<User> {
    // ...
}

I really don't want to have to go back to writing .into_inner() again. It's just noise.

[abonander]

@robjtede I see the discussion in #2016 but I don't think making the field private was necessary, it can just be a style suggestion in the docs to not access tuple fields directly. Paths with multiple parameters should probably switch to using structs anyway.

[robjtede]

Sorry I'm not considering this change at this time. The discussion in #2016 remains true.