-
-
Notifications
You must be signed in to change notification settings - Fork 6.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG][KOTLIN] NullPointerException generating model documentation for enum value named null
#11625
Comments
what is the status of this issue? |
Encountered the same issue in 6.1.0. Can be worked around by deleting the |
@Marek00Malik I don't think anyone has started working on a fix. Would you have time to contribute a fix? |
Hey guys. |
Any progress? 👀 I got the same issue when I tried to generate my own client for GitHub API (I know there is existing GitHub java library, but I am just using GitHub OpenAPI spec to practice using this openapi-generator) |
Encountered the same issue. Any update? |
Would anyone like to sponsor @Marek00Malik to come up with a fix with a higher priority? |
no longer seeing the same issue with the latest v7.0.0 so closing this. |
Bug Report Checklist
Description
I'm generating a client for a 3rd party API I do not own. They are using nullable enum properties in their API, with
null
as a possible enum value.The Kotlin generator is able to generate the model successfully, but the generator fails afterwards when generating the model documentation.
Resulting Model:
NullPointerException:
openapi-generator version
5.4.0
OpenAPI declaration file content or url
Generation Details
Steps to reproduce
enum
property andnull
as a possible value for the enum.kotlin
/multiplatform
client for the API.Related issues/PRs
I have not found related or open PR.
Suggest a fix
I'm guessing this has to do with parsing the
null
as a field name in the documentation. But I am not familiar with the doc generation to suggest a fix. FWIW this issue does not appear in the Java generators.The text was updated successfully, but these errors were encountered: