Skip to content

FromRequestParts derive macro uses wrong rejection #3160

Open
@Turbo87

Description

@Turbo87
  • I have looked for existing issues (including closed) about this

Bug Report

Version

0.8.1

Crates

axum-macros

Description

https://docs.rs/axum/latest/axum/extract/derive.FromRequest.html#the-whole-type-at-once claims that:

The rejection will be the “via extractors”’s rejection. For the previous example that would be axum::extract::rejection::ExtensionRejection.

but from what I've found, this is incorrect. I've tried to use #[from_request(via(Query))] on a struct, assuming that the corresponding rejection would be QueryRejection, but instead axum::response::Response was put in the derived impl (documented as the default at https://docs.rs/axum/0.8.1/axum/extract/derive.FromRequest.html#the-rejection).

I assume that this is a bug in the derive macro for at least FromRequestParts, but probably FromRequest too.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions