Skip to content

Support for building complex types #6

@sazzer

Description

@sazzer

I'm using this with the Clerk API, and it's working well. However, I'm just about to implement something that does a PATCH of a user, which means I need to construct a UpdateUserRequest but only populate 2 fields - out of 27.

Because the generated UpdateUserRequest doesn't derive Default or have any structured way of building it, this means that I've got to specify all 27 fields, but pass None into 25 of them.

Having some better way to handle this would be hugely useful if that's at all possible.

Cheers

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions