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
It appears there is a bug in okhttp templates or some upstream code: ".value" is being added after paramName when isEnum set to true. This happens even if type of paramName being collection containing enum values. So I guess there has to be some combination of isEnum and isContainer conditionals. I'm not that proficient in mustache templating so I guess better I could do is to open a dedicated issue. For sake of this PR I've changed values in api spec from list of enums to list of strings.
Bug Report Checklist
Have you provided a full/minimal spec to reproduce the issue?
Have you validated the input using an OpenAPI validator (example)?
Rattenkrieg
changed the title
[BUG] Description
[BUG] for kotlin okhttp client ".value" is being added after paramName for default values of List<Enum> type
Sep 4, 2022
I think I have the same issue. For me it generates invalid code because enum is nullable and no safe call is used: "nullableEnumParam" to PartConfig(body = nullableEnumParam.value, headers = mutableMapOf()),)
Description
Followup for #13243
Bug Report Checklist
openapi-generator version
6.0.1
commit 2a007b3
OpenAPI declaration file content or url
Related issues/PRs
#13243
The text was updated successfully, but these errors were encountered: