Ferdi Koomen

@firmbase-tal By default OpenAPI does not allow you to export 'named' enum values, instead they rely only on values. You can use enum names by using something like `x-enum-varnames`: ```...

@Piranit Correct, the generator does not support this at the moment. How do you use the header? Normally these headers are referenced inside a Operation object, do you have an...

@webpro I'm not against exposing separate files, however the API for each method is not what i consider "public" only the main method and CLI commands are supported. I know...

@khanab85 It seems there is indeed a circular reference in the models. I quickly looked into this, but there seems to be something interesting with the composition of the models....

@altarrok There is a fix for that in the current development branch (complex query params support). This should fix your issue. Once i have a few more things fixed i...

@altarrok New version is pushed to NPM 0.13.0 Could you check if that resolves your issue?

@altarrok New version is pushed 0.15.0, that should include all options (nested props, arrays, etc.)

@altarrok do you by change have a link to the spec or a copy of the spec that i can check? Im mostly interested in the definition of that parameter....

@altarrok I assume you then have something like this in the operation parameters right?: ``` "parameters": [ { "description": "This is a pageable parameter", "name": "pageable", "in": "query", "schema": {...

@altarrok When im using the latest version (0.18.1), then i see the following behaviour When im sending the following parameter: ``` parameter: { page: '0', size: '1', sort: ['location'] }...