William-Froelich

I'm also seeing this issue. Our API relies heavily on `DisallowNull`.

The [documentation ](https://github.com/Azure/azure-functions-openapi-extension/blob/4e81588f399f642236e354f00f64de99dccb859a/docs/openapi-core.md) for azure-functions-openapi-extensions states that `.DisallowNull` indicates a field is always required. but from the Newtonsoft Documentation, this statement is wrong: From [Src/Newtonsoft.Json/Required.cs](https://github.com/JamesNK/Newtonsoft.Json/blob/f7e7bd05d9280f17993500085202ff4ea150564a/Src/Newtonsoft.Json/Required.cs) ``` // // Summary: //...

https://github.com/Azure/azure-functions-openapi-extension/issues/336 relates to this issue.

I wiped out my system and installed dotnet 7 and that seems to have resolved the build issue for me.

@justinyoo I just looked over [ OpenAPI spec for parameters](https://swagger.io/docs/specification/describing-parameters/) and I disagree with that assessment. There's a `required` property and as of OpenAPI version 3 a `nullable` property. `required`...

@justinyoo have you had any time to look into this further and look over what I posted? How can I help get this resolved faster?

Sure, I'll update the PR. Would you prefer I add it to the `ObjectTypeVisitor` and `RecursiveObjectTypeVisitor` classes or somewhere else?