Spring Data REST PageMetadata doesn't preserve projection parameter for first, next, prev links [DATAREST-780]

Marc Zampetti opened DATAREST-780 and commented

When using the Collections resource of an Repository exposed via Spring Data REST, and one is using a projection as part of the query, the _links that are generated do not include the used projection. So any application that is trying to follow the HAL principals and use the _link metadata to page through the results will break since the expected output will change on pages 2 - N because the projection is no longer applied.

For example (NOTE URLs modified to remove some identifying info we don't want exposed):

GET /connect/avails?projection=ipm&size=1

returns 

_links: {
     first: {
          href: "/connect/avails?page=0&size=1"
     },
     self: {
          href: "/connect/avails"
     },
     next: {
          href: "/connect/avails?page=1&size=1"
     },
     last: {
          href: "/connect/avails?page=308429&size=1"
     },
     profile: {
          href: "/connect/connect/profile/avails"
     },
     search: {
         href: "/connect/avails/search"
     }
}

Affects: 2.4.2 (Gosling SR2)

1 votes, 2 watchers