Optional boolean as query parameter

[allenpsuner]

I have an optional boolean query param in a GetAll Models function in this format:

        [ResponseType(typeof(IEnumerable<Foo>))]
        public IEnumerable<Foo> GetAll(bool? myBool = null)
        {
            if (myBool.HasValue)
            {
                return Repository.GetAll(Url).Where<Foo>(foo => foo.myBoolValue.Equals(myBool));
            }
            else
            {
                return Repository.GetAll(Url);
            }
        }

But in the swagger UI it doesn't behave like a true nullable.

Is this a bug that is being worked on? Or is there a possible workaround that I should be using?

[monobjorn]

Maybe this has to do with Swagger UI? Have a look at: non-required Boolean value is always selected #1191

[allenpsuner]

Maybe I should give some context. I'm using Swashbuckle because I heard that it was super easy to integrate into my .NET WebApi project. I'm pretty sure there are no YAML configs for Swashbuckle, so that thread doesn't really help me out. I'm 99% sure that this isn't a bug and I'm just doing something wrong, but Stack-Overflow wasn't being responsive quick enough.

[monobjorn]

I'm also new to Swashbuckle (just started using it the day before yesterday).
Swashbuckle generates a JSON specification of your service. This corresponds to the YAML mentioned in the issue.

I tried adding an optional boolean to my project and I got the same issue that you had. I then downloaded the newest version of swagger-ui and then it worked. So, it's not actually a Swashbuckle-issue.

[domaindrivendev]

@monobjorn is absolutely correct - this was a swagger-ui issue as opposed to a bug in SB itself.

I've upgraded to the latest swagger-ui and the issue is fixed. It will be available with the next release which I'm working hard to get out ASAP.

[allenpsuner]

Awesome. Thank you so much @domaindrivendev.

[domaindrivendev]

Should be resolved in latest release - 5.2.0