This repository has been archived by the owner on Jan 21, 2020. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 49
Page query param added to collection self link #90
Comments
Actually, neither the first nor the self page should have the parameter at that point. I'm not quite sure how we'll address that, though. |
Currently I solved it by customizing the
And on top of that I removed the page param from the self route...
Not sure if this could be of any help, but for now it did the job for me. |
This repository has been closed and moved to laminas-api-tools/api-tools-hal; a new issue has been opened at laminas-api-tools/api-tools-hal#20. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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: