Icy Posts - Answer Overflow

Icy

Explore posts from servers

•Created by Icy on 3/26/2025 in #help

Generated OpenAPI document uses PascalCase instead of camelCase on requestBody properties

Hello, I'm still new to .NET and I've been trying to solve this issue for 2 days now. I'm using .NET's Microsoft.AspNetCore.OpenApi package for generating OpenAPI document. It automatically serializes all model properties to camelCase, except for requestBody. I have an upload controller that receives form data:

[HttpPost]
public async Task<IActionResult> UploadData([FromForm] UploadData data)
...

[HttpPost]
public async Task<IActionResult> UploadData([FromForm] UploadData data)
...

and the model looks like this:

public class UploadData {
  public string? Title { get; set; }
  public string? Description { get; set; }
  public required List<IFormFile> Files { get; set; }
}

public class UploadData {
  public string? Title { get; set; }
  public string? Description { get; set; }
  public required List<IFormFile> Files { get; set; }
}

I tried using [JsonPropertyName("title")] decorator on model properties, but that doesn't seem to affect the generated document. Also tried specifying options.JsonSerializerOptions.PropertyNamingPolicy = JsonNamingPolicy.CamelCase; as AI keeps suggesting, but that doesn't seem to work either. Does anyone know how I could solve this issue?

2 replies

HHono

•Created by Icy on 2/24/2025 in #help

How to handle file uploads

There's a very brief documentation on file upload, however it doesn't cover how to store files on the disk. Of course I could use native Node modules, like fs however my biggest problem is that it's all done in memory. I've also noticed that when using req.parseBody, if there are multiple large size files being uploaded, the server response time for other endpoints increases drastically. So what would be the correct way to handle file uploads, while avoiding storing files in the memory?

44 replies

Gaming

Programming