Pagination not including a previous element when expected

[joelgilchrist]

I do a search and it returns valid results with a next element.

$ curl -s -H "Authorization: Bearer xxx" "https://api.gitbook.com/v1/spaces/yyy/search?query=order"

...
        ],
        "next": {
            "page": "1"
        }
    }
}

Then I append page=1 and rerun the search.

$ curl -s -H "Authorization: Bearer xxx" "https://api.gitbook.com/v1/spaces/yyy/search?query=order&page=1"

...
    ],
    "next": {
        "page": "2"
    }
}

Shouldn't there be a:

    "previous": {
        "page": "1"
    }

[SamyPesse]

Our pagination logic does not support previous for all endpoints. For many of our API endpoints (depending on the underlying data source), we only return next.
It constraints the UI that can be build on top of it, the suggestion in that case is to build it as a "infinite list" UI where fetching the next pages append the results to a long list instead of just displaying the current page.

[joelgilchrist]

Thanks. This is helpful. It would be better to update the pagination link with this information. Right now it reads as if previous and next are always included.