[littlegrasscao]

Summary

• the provider list endpoints (GET /shares, GET /shares/{share}/permissions and GET /recipients) took maxResults as an Integer, which Armeria parses before the endpoint runs, so a value such as ten was 400 with Java's parse message (For input string: "ten")
• new Pagination.maxResults reads the query parameter instead: a value that is not an integer is 400 INVALID_PARAMETER_VALUE with the message maxResults must be an integer, and an empty value counts as unset
• the endpoints now take maxResults as a string and read it through Pagination.maxResults; the paging rules are unchanged
• the recipient protocol list endpoints (OpenSharing protocol: authenticate recipients and list granted shares #101 onwards) reuse the same helper

Testing

• mvn clean verify: 127 tests passed
• ProviderMaxResultsTest: ten, 1.5 and an out-of-range 3000000000 are 400 with the new message on all three lists, and an empty maxResults lists as if unset

[littlegrasscao]

Dropped: the provider and protocol list endpoints keep the typed @PARAM Integer maxResults; a non-integer value is already 400 INVALID_PARAMETER_VALUE, and only the message wording would differ.