Uh oh!
There was an error while loading. Please reload this page.
Fixes invalid Kotlin client variable names for reserved words - #3993
Conversation
The Kotlin Multiplatform client introduced an bug that rendered variable names that were also Kotlin reserved words incorrectly. This change reverts the template to use the previous mechanism for rendering variable names. OpenAPITools#3992
andrewemery
commented
Sep 30, 2019
@wing328 Apologies. I introduced a breaking change to Kotlin clients with the addition of Kotlin Multiplatform. The original branch (from Swagger Codegen) required a workaround to escape Kotlin identifiers. This workaround is no longer necessary (on OpenAPI) and breaks existing Kotlin clients that have identifers that are Kotlin reserved words. This change removes the workaround in favour of the existing approach. |
wing328
commented
Oct 1, 2019
That's ok. Thanks for letting us know and the quite fix. |
wing328
commented
Oct 1, 2019
The fix looks good. |
…ITools#3993) The Kotlin Multiplatform client introduced an bug that rendered variable names that were also Kotlin reserved words incorrectly. This change reverts the template to use the previous mechanism for rendering variable names. OpenAPITools#3992
wing328
commented
Oct 4, 2019
@andrewemery thanks for the PR, which has been included in the v4.1.3 release: https://twitter.com/oas_generator/status/1180123829626003456 |
The Kotlin Multiplatform client introduced an bug that rendered variable names that were also Kotlin reserved words incorrectly. This change reverts the template to use the previous mechanism for rendering variable names.
#3992