Skip to content

non-obvious error when passing invalid 'previous' or 'next' tokens #118

Open
@bradvogel

Description

@bradvogel

When passing an incorrect value such as 'next=NOT_REAL_TOKEN', this library will throw the exception Unexpected token } in JSON at position 0. It would be better if it threw a more obvious error such as "Invalid valid for 'next'"

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions