@ryanfox one workaround is to document the query parameter as a string instead of boolean and users will need to input either "true" or "false"

Another way is to use customized templates with the -t option and add logic to normalize the values inside the following mustache tag:

{{#isBoolean}}
...
{{/isBoolean}}

Thanks for the info. That's not going to work for the use case I am working with - what do you think the chances are of implementing a fix?

In any case, good to know there is a workaround.

@ryanfox why would the string solution not work in your use case?
Why not make it a string enum?

      - name: "reverse"
        in: "query"
        description: 'If true, will sort results newest first.'
        required: false
        default: "false"
        type: "string"
        enum:
        - "true"
        - "false"

@spacether Perhaps because it adds a lot of noise to the spec, lies to every tool involved including the API generator, and generally just smells of a massive, dirty hack? :))

Not saying that it shouldn't be fixed. My goal was to provide solution that unblocks Ryan.
We welcome any PRs that fix issues. Do you want to work on fixing this @ryanfox or @mcejp ?