You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 21, 2020. It is now read-only.
The url I requested was http://hostname/api/v1/users. The self link in the response gets a pagination param while the first page doesn't. Shouldn't it be the other way around?
So like this:
On the client I would like to dynamically create links to my other pages by adding a page query parameter including a page number to the collection self link. Right now I cannot do this because the self link already holds a page param. I would expect the self link to be a base collection link.
The text was updated successfully, but these errors were encountered:
When I request a collection route while using pagination I get the links rendered as follows:
The url I requested was
http://hostname/api/v1/users
. The self link in the response gets a pagination param while the first page doesn't. Shouldn't it be the other way around?So like this:
On the client I would like to dynamically create links to my other pages by adding a
page
query parameter including a page number to the collection self link. Right now I cannot do this because the self link already holds apage
param. I would expect the self link to be a base collection link.The text was updated successfully, but these errors were encountered: