-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Support for [FromForm] in Minimal API #4626
Comments
Also encountering the same issue, would like this to be fixed if possible. |
Hi, I'm experiencing the same issue. Is there any advice or direction on where to look to make it work with minimal API? It seems it works correctly with the controllers though. |
Are there any news on this? |
Personally I swapped to Swashbuckle, and will swap over to the built-in support in .Net 9 as soon as possible. |
Yeah, Swashbuckle does not support nullable reference types fully - in the future the built-in functionality may be a viable solution, but that won't be happening with .NET 9. Migrating existing projects may also not be that easy. |
Please fix this! |
any update on this issue ? |
Love me a blocking dead issue |
- Preemptively made comment handlers use primary constructors to make move to `Immediate.Apis` easier - Partially moved ratings to `Immediate.Apis`, blocked by RicoSuter/NSwag#4626
Hi, I'm creating a new .Net 8 minimal API-based web API and I'm having trouble getting NSwag to generate
multipart/form-data
schemas - they're generating as query parameters instead.This works with Swashbuckle despite not having an update almost a year.
The text was updated successfully, but these errors were encountered: