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
I just noticed that the spring data interface pageable uses int for page number and page size, but the PageMetaData from the PagedModel in spring hateoas uses long for size, totalElements, totalPages and number.
This makes in unnecessary hard to combine both paging approaches within the spring libs.
In terms of expected values it won't be a problem to simply cast, one to the other, because you seldom would have more pages than max_int.
Nevertheless, this would be good to harmonize.
This is why I created the issue here, because it should be better to upgrade ints to long, than reduce the long to int. (even though it should hopefully not lead to errors)
The text was updated successfully, but these errors were encountered:
I just noticed that the spring data interface pageable uses int for page number and page size, but the PageMetaData from the PagedModel in spring hateoas uses long for size, totalElements, totalPages and number.
This makes in unnecessary hard to combine both paging approaches within the spring libs.
In terms of expected values it won't be a problem to simply cast, one to the other, because you seldom would have more pages than max_int.
Nevertheless, this would be good to harmonize.
This is why I created the issue here, because it should be better to upgrade ints to long, than reduce the long to int. (even though it should hopefully not lead to errors)
The text was updated successfully, but these errors were encountered: