Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Implement IntoResponse for MultipartError #1851

Closed
davidpdrsn opened this issue Mar 13, 2023 · 0 comments · Fixed by #1861
Closed

Implement IntoResponse for MultipartError #1851

davidpdrsn opened this issue Mar 13, 2023 · 0 comments · Fixed by #1861
Labels
A-axum A-axum-extra C-feature-request Category: A feature request, i.e: not implemented / a PR. E-medium Call for participation: Experience needed to fix: Medium / intermediate

Comments

@davidpdrsn
Copy link
Member

See #1847 for context.

Should be done both for the Multipart in axum and axum-extra.
@davidpdrsn davidpdrsn added C-feature-request Category: A feature request, i.e: not implemented / a PR. E-medium Call for participation: Experience needed to fix: Medium / intermediate A-axum A-axum-extra labels Mar 13, 2023
davidpdrsn added a commit that referenced this issue Mar 17, 2023
@davidpdrsn
Implement IntoResponse for MultipartError
481360f 
So you can return `MultipartError` from handlers without having to
downcast the errors yourself.

Fixes #1851
@davidpdrsn davidpdrsn mentioned this issue Mar 17, 2023
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
A-axum A-axum-extra C-feature-request Category: A feature request, i.e: not implemented / a PR. E-medium Call for participation: Experience needed to fix: Medium / intermediate
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Implement IntoResponse for MultipartError tokio-rs/axum
1 participant
@davidpdrsn