Skip to content
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

Fix: Handle unset union map type #650

Merged
merged 1 commit into from Jul 25, 2022

Conversation

jamietanna
Copy link
Collaborator

Without this check, an uninitialised (zero-value) t.union will get
serialised as null, which then overrides the map's contents, leading
to a panic:

panic: assignment to entry in nil map

By instead only unmarshalling this when we receive a non-nil version of
the t.union, we can handle zero-value'd structs.

Without this check, an uninitialised (zero-value) `t.union` will get
serialised as `null`, which then overrides the map's contents, leading
to a panic:

  panic: assignment to entry in nil map

By instead only unmarshalling this when we receive a non-nil version of
the `t.union`, we can handle zero-value'd structs.
Copy link
Contributor

@Warboss-rus Warboss-rus left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This only affects cases with oneOf\anyOf and regular properties in the same object, in case union type was not initialized. Thanks for the fixes!

@deepmap-marcinr deepmap-marcinr merged commit 91b48ba into deepmap:master Jul 25, 2022
adrianpk pushed a commit to foorester/oapi-codegen that referenced this pull request Jan 16, 2024
Without this check, an uninitialised (zero-value) `t.union` will get
serialised as `null`, which then overrides the map's contents, leading
to a panic:

  panic: assignment to entry in nil map

By instead only unmarshalling this when we receive a non-nil version of
the `t.union`, we can handle zero-value'd structs.
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.

None yet

4 participants