CamelCase naming when using form data

[UltraWelfare]

In such scenario:

// Controller code
[HttpPost]
[Consumes(MediaTypeNames.Multipart.FormData)]
[ProducesResponseType<ProjectData>(StatusCodes.Status200OK)]
[ProducesResponseType(StatusCodes.Status403Forbidden)]
public async Task<Ok<ProjectData>> CreateProject(
    [FromForm] CreateProjectRequest request
    )

// CreateProjectRequest code
public record CreateProjectRequest
{
    public required string Title { get; init; }
    public required string Description { get; init; }
    public required int? CategoryId { get; init; }
    public required IFormFileCollection Files { get; init; } = new FormFileCollection();
}

The generated json is as follows:

"post": {
  "tags": [
    "Project"
  ],
  "requestBody": {
    "content": {
      "multipart/form-data": {
        "schema": {
          "required": [
            "Description",
            "Files",
            "Title"
          ],
          "type": "object",
          "properties": {
            "Title": {
              "type": "string"
            },
            "Description": {
              "type": "string"
            },
            "CategoryId": {
              "type": "integer",
              "format": "int32"
            },
            "Files": {
              "type": "array",
              "items": {
                "type": "string",
                "format": "binary"
              }
            }
          }
        },
        "encoding": {
          "Title": {
            "style": "form"
          },
          "Description": {
            "style": "form"
          },
          "CategoryId": {
            "style": "form"
          },
          "Files": {
            "style": "form"
          }
        }
      }
    }
  },

How can I change it so that it generates the properties in camelCase?

[martincostello]

How have you configured the JSON serialization options for your application?

[UltraWelfare]

To be absolutely honest no. The endpoints that required JSON objects as requests worked fine as camelcase by default.
However I tried adding the following:

builder.Services.Configure<JsonOptions>(options =>
{
    options.SerializerOptions.Converters.Add(new JsonStringEnumConverter());
    options.SerializerOptions.PropertyNamingPolicy = JsonNamingPolicy.CamelCase;
});
builder.Services.AddControllers().AddJsonOptions(options =>
{
    options.JsonSerializerOptions.Converters.Add(new JsonStringEnumConverter());
    options.JsonSerializerOptions.PropertyNamingPolicy = JsonNamingPolicy.CamelCase;
});

I assume since it's form data, it doesn't respect the JsonSerializerOptions ? Which makes sense, but where do I configure it to also change for form data?

[martincostello]

I'm not aware of a way to do that in MVC (but maybe there is one) - if there is and then Swashbuckle doesn't match it then that's a bug on our end.