Stack Apps is a question and answer site for apps, scripts, and development with the Stack Exchange API. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

As far as I can tell, there can only be one info object returned from the info method, so why does the method take page and page_size?

share|improve this question
up vote 0 down vote accepted

While technically they work, they don't do much of value. I'd keep them around for symmetry if they were the only method in the API which didn't need them, but they're already missing from other methods where they're nonsensical.

They'll be pulled in the next deploy, with page and pagesize on the wrapper set to 1 (if they're requested).

share|improve this answer
Uhm... does this mean the API will reject requests for /info that containg page=1? Stack.PHP's class structure expects to be able to supply pagination parameters to all methods. – Nathan Osman Dec 14 '11 at 18:55
@George - no it won't reject them, it will just ignore them. Note that pagination doesn't exist on /errors/{id} or filter/create either. – Kevin Montrose Dec 14 '11 at 18:59
Ah, okay. The users of my library should never be specifying a page number for the requests - it's just that the class keeps track of page numbers internally and by default sends the page=1 parameter for the first request. – Nathan Osman Dec 14 '11 at 19:03

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .