Bug: Inconsistent response type for field per_page

[omani]

Passing query param per_page results in different type of said param. per_page is an integer in a normal response but suddenly a string in the response of a request where per_page is passed as a query param.

[omani]

a little observation: if I pass a per_page > 250 (which seems to be a hard limit on the backend), I get a normal integer back, even though I passed the param. but param per_page set to eg. 10, gives back a string.

so it seems that a per_page that has been set, is being passed back as a string.

example returning an integer:
curl -X GET -G "https://openapi.nkn.org/api/v1/transactions" -H "Content-Type: application/json" -H "Accept: application/json" | jq

"first_page_url": "https://openapi.nkn.org/api/v1/transactions?page=1",
"from": 1,
"next_page_url": "https://openapi.nkn.org/api/v1/transactions?page=2",
"path": "https://openapi.nkn.org/api/v1/transactions",
"per_page": 10,
"prev_page_url": null,
"to": 10

example returning a string:
curl -X GET -G "https://openapi.nkn.org/api/v1/transactions?per_page=10" -H "Content-Type: application/json" -H "Accept: application/json" | jq

"first_page_url": "https://openapi.nkn.org/api/v1/transactions?page=1",
"from": 1,
"next_page_url": "https://openapi.nkn.org/api/v1/transactions?page=2",
"path": "https://openapi.nkn.org/api/v1/transactions",
"per_page": "10",
"prev_page_url": null,
"to": 10

notice the difference:
"per_page": 10, and "per_page": "10",