Limit doesn't work

[benjaminledet]

Hi, when I call an api endpoint like "https://pokeapi.co/api/v2/pokemon/", I'm getting the full list of Pokemon or the doc says :
"Calling any API endpoint without a resource ID or name will return a paginated list of available resources for that API. By default, a list 'page' will contain up to 20 resources. If you would like to change this just add a 'limit' query parameter, e.g. limit=60."

I tried to set the limit too but it doesn't work neither.
Am I doing something wrong?
thanks

[cmmartti]

Hi, this is a side effect of the outage we had this week. As a quick fix we put the static JSON files on the server. We are in the process of moving to static hosting (see #350) on Netlify, but we're not quite ready to move to that yet. Until then, pagination will probably remain broken.

[benjaminledet]

ok thanks for this very quick answer!

[tdmalone]

Related: #365

[tdmalone]

I'm going to close this issue as there is nothing actionable for us at the moment. As @cmmartti mentioned, it will be fixed as soon as we move to Netlify. Apologies in the meantime!

[vitro-dynamics]

so what does this mean?

[cmmartti]

@sargtier1 It means that queries that include either ?limit=100 or ?offset=100 (any numbers) will not respect the requested page and will instead return the entire result set, however large it is. This is temporary and will probably be fixed by the end of the week or next week.

[vitro-dynamics]

@sargtier1 It means that queries that include either ?limit=100 or ?offset=100 (any numbers) will not respect the requested page and will instead return the entire result set, however large it is. This is temporary and will probably be fixed by the end of the week or next week.

thanks for the feed back brother!

[cbouwense]

Is this still an issue

[tdmalone]

@cbouwense Yes it is - it will be until we complete our move to static hosting, which is hopefully going to be shortly!

[Kronopt]

This shouldn't be closed as it is still an issue.