Skip to content

fix: include-if-null-spec-nullable - #845

Open
Mastersam07 wants to merge 25 commits into
epam-cross-platform-lab:masterfrom
bushaHQ:master
Open

Mastersam07 wants to merge 25 commits into
epam-cross-platform-lab:masterfrom
bushaHQ:master

Conversation

@Mastersam07

Copy link
Copy Markdown

Current behaviour

When include_if_null was set to false globally, fields explicitly marked nullable: true in the OpenAPI spec would have their null values omitted during serialization. This is incorrect because the spec author declared null as a valid, intentional value for those fields.

Incoming/Expected behaviour

Fields with spec-declared nullability (nullable: true or type array containing null) get includeIfNull: true regardless of the global setting, ensuring null values are always serialized for those fields.

fix: `includeIfNull: false` silently dropping null values for spec-nu…
fix: add index, name, and values to enum exception words
Previously, any list property on a class whose name ends with `$Item`
was generated as `List<Object>` even when items resolved to a typed
enum or primitive. Tighten the short-circuit so it fires only when
`items.properties` is non-empty (i.e. items is actually a nested
object), letting the normal type resolution emit `List<enums.X>` /
`List<String>` / `List<int>` / etc.
fix: narrow $Item list-type guard to nested-object items only
fix: type array item enum query parameters and comma-join non-exploded lists
fix: type referenced array enum query parameters as lists
fix: skip enum values without a wire value when serializing lists
feat: generate sealed unions for oneOf schemas behind generate_one_of_unions
…anches, text bodies and array-response enums
feat: type oneOf array items, request bodies, responses and nullable branches
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant