Should the handbook be more explicit about Link Header construction?
If an additional URL parameters such sort, filters, or fields are requested, should the Link header include the URL param as part of the pre-constructed links.
Example:
GET /artists?sort=-name
Response Link Header:
<https://dev.api.jukebox.540.co/v1/artists?&sort=-name&limit=10&offset=0>; rel="first",<https://dev.api.jukebox.540.co/v1/artists?&sort=-name&limit=10&offset=110>; rel="last",<https://dev.api.jukebox.540.co/v1/artists?&sort=-name&limit=10&offset=10>; rel="next"
Should the handbook be more explicit about Link Header construction?
If an additional URL parameters such
sort
,filters
, orfields
are requested, should the Link header include the URL param as part of the pre-constructed links.Example:
GET /artists?sort=-name
Response Link Header:
<https://dev.api.jukebox.540.co/v1/artists?&sort=-name&limit=10&offset=0>; rel="first",<https://dev.api.jukebox.540.co/v1/artists?&sort=-name&limit=10&offset=110>; rel="last",<https://dev.api.jukebox.540.co/v1/artists?&sort=-name&limit=10&offset=10>; rel="next"