fix: support boolean schemas

[emonadeo]

oazapfts codegen fails if the api contains boolean json schema.

{
  // ...
  "schemas": {
    "Foo": {
      "type": "object",
      "required": ["bar"],
      "properties": {
        "bar": true
      },
      "additionalProperties": false
    }
  }
}

This PR adds support for these, mapping true to any and false to never.

I am not sure about how this should behave with "TrueEnums" (not sure what that is i get it now, these are typescript enums), so please review with extra care, as I am not familiar with the codebase and don't understand every corner of it.

This is an upstream issue with kogosoftwarellc/open-api, which is also missing boolean schema support (I filed a PR to fix this at kogosoftwarellc/open-api#902).

[Xiphe]

Hi @emonadeo!

Thank you for the contribution and sorry for the late reply, I currently don't have much capacity for this project.

Could you help me wrap my head around why and where this is useful in the context of Open API Spec?
I don't want to imply, it's not useful. At the same time, as a maintainer of this I try to understand how people use the Spec and what they feed into the codegen and why.

[emonadeo]

I personally don't use boolean json schema but others do and some codegen tools use it as well. Right now oazapfts just errors when trying to generate a client from such an openapi file.

[Xiphe]

Solid work! I have some minor change requests 🤓

[github-actions]

🎉 This PR is included in version oazapfts-v6.1.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀