axum/axum-macros/tests/from_request/fail/unknown_attr_container.stderr

error: expected one of: `via`, `rejection`, `state`
 --> tests/from_request/fail/unknown_attr_container.rs:4:16
  |
4 | #[from_request(foo)]
  |                ^^^
Support `State` with `#[derive(FromRequest[Parts])]` (#1391) * Support `State` with `#[derive(FromRequest[Parts])]` Fixes https://github.com/tokio-rs/axum/issues/1314 This makes it possible to extract things via `State` in `#[derive(FromRequet)]`: ```rust struct Foo { state: State<AppState>, } ``` The state can also be inferred in a lot of cases so you only need to write: ```rust struct Foo { // since we're using `State<AppState>` we know the state has to be // `AppState` state: State<AppState>, } ``` Same for ```rust struct Foo { #[from_request(via(State))] state: AppState, } ``` And ```rust struct AppState {} ``` I think I've covered all the edge cases but there are (unsurprisingly) a few. * make sure things can be combined with other extractors * main functions in ui tests don't need to be async * Add test for multiple identicaly state types * Add failing test for multiple states 2022-09-23 23:50:50 +02:00			error: expected one of: `via`, `rejection`, `state`
Support opt-out of extra derived traits for rejections for `#[derive(FromRequest)]` (#729) * Handle structs without fields * Support opt-out of derived rejection traits * Handle duplicate opt outs * Improve error if opting out of `Display` or `Debug` but not `Error` * document `rejection_derive` * Handle using both `via` and `rejection_derive` * don't derive debug for `RejectionDeriveOptOuts` * Update axum-macros/src/from_request.rs Co-authored-by: Jonas Platte <jplatte@users.noreply.github.com> Co-authored-by: Jonas Platte <jplatte@users.noreply.github.com> 2022-01-28 10:54:38 +01:00			`--> tests/from_request/fail/unknown_attr_container.rs:4:16`
			`\|`
			`4 \| #[from_request(foo)]`
			`\| ^^^`