Skip to content

Expose pagination options through the CLI global arguments #434

@displague

Description

@displague

We're not using the Servicer.Excludes/Includes functions in some of these pagination locations. This is needed to ensure that the --include and --exclude arguments from the CLI make it into the request.

We should introduce --page, --per-page as globals, like include and exclude. These would also be exposed through the Servicer to pass the desired pagination settings into the request. This would allow a user to skip the full list or paginate on their own terms. Sort options (sort_by, sort_dir) would also make sense with --page.

A difference between pagination options and include/excludes, is that the latter are used in all request types while pagination is only used in GET requests.

Originally posted by @displague in #431 (comment)

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