missing parameter declarations causing issues generating client libs from openapi spec files

[AzothZephyr]

gm,

was trying to create client libraries off of the openapi specs tonight and ran into some errors while using openapi-generator. one error i ran into is a known openapi bug, which i'll get to at the end, the other was a lack of path parameter declarations on numerous endpoints in the ir and md spec files.

i manually fixed but seeing as these files appear to be programmatically generated, i'm not going to post a pr. changes can be viewed on my fork of this repository. unfortunately, they are the last two files so you'll have to do some scrolling.

fixed errors that crop up:

-paths.'/users/subaccount/{subaccount_id}/fills'. Declared path parameter subaccount_id needs to be defined as a path parameter in path or operation level
-paths.'/users/subaccount/{subaccount_id}/deposits'. Declared path parameter subaccount_id needs to be defined as a path parameter in path or operation level
-paths.'/users/subaccount/{subaccount_id}'. Declared path parameter subaccount_id needs to be defined as a path parameter in path or operation level
-paths.'/users/subaccount/{subaccount_id}/transfers'. Declared path parameter subaccount_id needs to be defined as a path parameter in path or operation level
-paths.'/users/subaccount/{subaccount_id}/positions'. Declared path parameter subaccount_id needs to be defined as a path parameter in path or operation level
-paths.'/users/subaccount/{subaccount_id}/orders'. Declared path parameter subaccount_id needs to be defined as a path parameter in path or operation level
-paths.'/users/subaccount/{subaccount_id}/withdrawals'. Declared path parameter subaccount_id needs to be defined as a path parameter in path or operation level
-paths.'/users/fee-estimate/{market-id}'. Declared path parameter market-id needs to be defined as a path parameter in path or operation level
-paths.'/book/{market_id}/snapshot'. Declared path parameter market_id needs to be defined as a path parameter in path or operation level
-paths.'/parsed/book/{market_symbol}/snapshot'. Declared path parameter market_symbol needs to be defined as a path parameter in path or operation level
-paths.'/parsed/book/{market_symbol}/recent-trades'. Declared path parameter market_symbol needs to be defined as a path parameter in path or operation level
-paths.'/book/{market_id}/recent-trades'. Declared path parameter market_id needs to be defined as a path parameter in path or operation level

unfixed errors that crop up (i think) as a result of a known openapitools issue. i tried fiddling around with various solutions that would make sense match the returned error message to no avail. what i have done to generate the client libs is skip validation after fixing the issues i could

-attribute paths.'/history/klines'(get).responses.200.content.'application/json'.schema.items is not of type `object`
-attribute paths.'/users/subaccount/{subaccount_id}'(get).responses.200.content.'application/json'.schema.items is missing
-attribute paths.'/history/klines'(get).responses.200.content.'application/json'.schema.items is missing
-attribute paths.'/users/info'(get).responses.200.content.'application/json'.schema.items is missing
-attribute paths.'/users/info'(get).responses.200.content.'application/json'.schema.items is not of type `object`
-attribute paths.'/users/subaccount/{subaccount_id}'(get).responses.200.content.'application/json'.schema.items is not of type `object`
-attribute paths.'/parsed/book/{market_symbol}/snapshot'(get).responses.200.content.'application/json'.schema.items is not of type `object`
-attribute paths.'/parsed/book/{market_symbol}/snapshot'(get).responses.200.content.'application/json'.schema.items is missing

i have yet to go down the openapi down convert side of the openapi spec file rabbit hole as its out of scope rn. is it possible that this could be incorporated into future builds so i can automate updates to the client libs i intend to use as you update the spec files here?

• az

[AzothZephyr]

here's a gist to show the errors that are generated when you don't have the skip validation flag. to reproduce, run the generate script. (note this will download the newest specs, leaving unstaged changes when comparing to my fork.)