Make WithRequestModel more granular

[eckersalld]

I may have missed something, but I can't see a way to make properties of the RequestModel required/optional, just the RequestModel itself?

So if I have model with properties of 'term' and 'section', where section is an optional filter to the required term, they will both appear as required in the documentation, when only term should be...

[Jaxelr]

Is your request model a Get operation? If so those are usually map through the query not the body and the RequestParameter provides a required default.

That being said the definition of RequestModel provides an optional parameter which may not be what you are looking for.

[kuskmen]

Hi guys,

maybe I am coming late, but I don't get it? Is there a way of saying some fields are optional in my request model? From what I see in the code there is none, except counting all the parameters one by one and marking them as optional.

Regards,
kuskmen

[Jaxelr]

On the metadata you can define multiple requestParameters per endpoint, like so:

            Describe["SimpleRequestWithParameter"] = desc => new SwaggerRouteMetadata(desc)
                .With(i => i.WithResponseModel("200", typeof(SimpleResponseModel), "Sample response")
                            .WithRequestParameter("param1")
                            .WithRequestParameter("param2", required: false, loc: "path")
                            .WithSummary("Simple GET with parameters"));