Skip to content

read, write: how about use some option pattern with request parameters? #8

Description

@tenkoh

Each request parameter such as ListParams have many fields. Users have difficulty to utilize them correctly. Split fields into required a nd optional will help them. ex) functional option pattern

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions