OpenAPI document generator does not account for required keyword when determining if a property is required

[thorhj]

Generated Open API definition does not mark properties as required if I use the required keyword on the properties.

Consider this request body type:

public record PatchUserRequest
{
  public string? Message { get; init; }
  public required int Age { get; init; }
}

When generating the Open API definition using NSwag, this type schema is generated:

      "PatchUserRequest": {
        "type": "object",
        "additionalProperties": false,
        "properties": {
          "message": {
            "type": "string",
            "nullable": true
          },
          "age": {
            "type": "integer",
            "format": "int32"
          }
        }
      }

Notice there are no required properties in this object. I think the usage of required on the property should add the property to the required list in the object schema. Right now I have to annotate the property with [Required] to get the desired effect.

With or without RequiredAttribute, deserialization to this object fails if "age" is omitted in the JSON if I use the default JSON serializer for ASP.NET (System.Text.Json). I think Open API document generation should match this behavior and mark these properties as required.

I think this can be solved by looking for the RequiredMemberAttribute in addition to RequiredAttribute when determining if a property is required or not. RequiredMemberAttribute is generated by the compiler for required properties.

[Alex69rus]

I'm struggling with the same issue.
@thorhj have you found any workaround (except RequiredAttribute) ?

[thorhj]

@Alex69rus Sorry, no.