Skip to content

Optional Enums in responses are not handled properly #56

@dbanty

Description

@dbanty

In 0.4.0-rc.1, if a server responds with an Optional Enum and provides null (not missing) it causes an error in the client.

Metadata

Metadata

Assignees

No one assigned

    Labels

    🐞bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions