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.

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

Fix allow response content_type without schema #1073

Merged
merged 1 commit into from
Oct 2, 2024

Conversation

juhaku
Copy link
Owner

@juhaku juhaku commented Oct 2, 2024

Fix allow response with content_type without schema.

 #[utoipa::path(post, path = "/api/secret", responses(
     (status = OK, content_type = "application/octet-stream")
 ))]
 async fn post_secret() {}

Fixes #965 Fixes #779

@juhaku juhaku force-pushed the fix-allow-response-content-type-without-schema branch from 85ed94e to d629865 Compare October 2, 2024 08:17
Fix allow response with `content_type` without schema.

```rust
 #[utoipa::path(post, path = "/api/secret", responses(
     (status = OK, content_type = "application/octet-stream")
 ))]
 async fn post_secret() {}
```

Fixes #965
@juhaku juhaku force-pushed the fix-allow-response-content-type-without-schema branch from d629865 to bfda9e8 Compare October 2, 2024 08:17
@juhaku juhaku merged commit 4147119 into master Oct 2, 2024
22 checks passed
@juhaku juhaku deleted the fix-allow-response-content-type-without-schema branch October 2, 2024 08:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Released
Development

Successfully merging this pull request may close these issues.

Content type not seted Examples not shown with IntoResponses
1 participant