I think you may be confused about the relationship between this project and the code it generates. This is something I will work to clarify in the readme and documentation.
This OpenAPI generator project is responsible for creating two types of modules: schemas and operations. In the example GitHub client, these modules can be found in lib/schemas and lib/operations. Everything outside of these directories is not generated code.
If you look through the modules in those directories, you will find no references to any HTTP client at all. In fact, the contract is a very general call to client.request/1, where client is a module configured or passed in as an option to the API operation. It is expected that a client library author (the customer of this project) will define their own client module using whatever tools they see fit.
In the GitHub client example, I’ve deliberately created a bring-your-own library system where anyone can define plugins to use any HTTP client they wish. It just so happens that I’ve only written an HTTPoison client out of the box for now.
