Skip to content

Why is accountId required for every retail API call? #9

@bramski

Description

@bramski

Seems redundant to me, why not just initialize the retail api instance with the accountId? Or provide a setter for it? Very annoying to have to pass that around with all the calls the instance will make.

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