You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi
I started using modeline to generate data classes in kotlin from async api document. When the field has Id as a suffix in it, the field name generated in data class doesn't do the camel casing properly for the class member.
Expected behavior
We would expect this tool to generate field names as the name given in the $id tag.
Screenshots
How to Reproduce
Provide an id to the field Name that ends with an Id e.g. $id: outletGSId
Run the kotlin data class generator
Observe the name in the data class. For me it is generating it as val outletGsId: String? = null,
However it should have been outletGSId
Welcome to AsyncAPI. Thanks a lot for reporting your first issue. Please check out our contributors guide and the instructions about a basic recommended setup useful for opening a pull request. Keep in mind there are also other channels you can use to interact with AsyncAPI community. For more details check out this issue.
gitankit7
changed the title
[BUG] Data class members overrides the variable name if it has Id in it [Kotlin Generator]
[BUG] Data class members name is changed to camel case even if an $Id is provided [Kotlin Generator]
Jul 27, 2024
Describe the bug.
Hi
I started using modeline to generate data classes in kotlin from async api document. When the field has
Id
as a suffix in it, the field name generated in data class doesn't do the camel casing properly for the class member.Expected behavior
We would expect this tool to generate field names as the name given in the $id tag.
Screenshots
How to Reproduce
Provide an id to the field Name that ends with an
Id
e.g. $id: outletGSIdRun the kotlin data class generator
Observe the name in the data class. For me it is generating it as
val outletGsId: String? = null,
However it should have been outletGSId
🥦 Browser
None
👀 Have you checked for similar open issues?
🏢 Have you read the Contributing Guidelines?
Are you willing to work on this issue ?
No, someone else can work on it
The text was updated successfully, but these errors were encountered: