Should required non-nullable properties be marked as required automatically

[royberris]

Should required non-nullable properties be marked as required automatically?

With the addition of the required keyword in .NET 7.
I have a required non-nullable string in one of my request bodies.

required public string Name { get; set; }

But this is still marked as nullable:

"parameters": [
  {
    "name": "Name",
    "in": "query",
    "schema": {
      "type": "string",
      "nullable": true
    },
    "x-position": 1
  },
]

For me it is logical that this is assumed to be not nullable in the API document from a software design perspective. What do you guys think?

[royberris]

Thinking about is, required does not mean a property is non-nullable. I can still have a required string? Name. Just means it has to be acted on when the type is initialized.

The question becomes, why is a non-nullable string nullable in the API document. Is this not known at runtime?

[royberris]

Next day I realized my mistake. The request was set to query parameters instead of a body. Adding [FromBody] to the parameter in the action solved the issue above and my idea was suddenly a feature already in this package.