Skip to content

Let consumers of the gem handle pagination #9

Description

@emilesilvis

Currently the gem paginates for you, often leading to the rate limit being hit and difficult-to-handle exceptions being thrown. While I think it's good to introduce an exception for when the rate limit is hit, I also think that pagination should be left up to the consumer of the gem (as mentioned here).

That way, we don't end up with being half-way through iterating through a collection and then getting the RateLimitError thrown. Plus, then it's a more faithful mirroring of the actual RESTful API.

Thoughts?

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