Mark property as required without the [Required] attribute

I understand that Swashbuckle supports the [Required] attribute on request model properties, i.e.

public class ChangeLineNumberViewModel
{
    /// <summary>
    /// The domain user who is changing the line number, i.e. TPWR\\johnd
    /// </summary>
    [Required]
    public string RequestedBy { get; set; }
}

However, [Required] signals to MVC model binding that the field is Required, and model binding intercepts the requests and gets in the way of my own internal validation which I wish to use (so that I can return a Problem details).

I guess what I’d like is perhaps a [SwaggerRequired] attribute I can use instead, so that the property is marked as required in the swagger doc.

[Snazzie]

@domaindrivendev That solution is not nice to use at all. Should there not be a way to set globally or a swagger variant of [Required] that doesnt affect .net model

[hlovdal]

@Snazzie, @mattfrear There is a custom [SwaggerRequired] attribute presented in this answer, although I agree this should be something that comes standard and not something that needs custom extra code.

Ideally there should also exist a [SwaggerOptional] attribute that does nothing but with some check than you then can configure to blow for anything that does not have one of the two attributes. Any suggestions how to achieve this?