Generators return a list of pages in various ways (page IDs, page titles, revision IDs); these pages might then get reloaded from the database to obtain additional data, and in the process the order of the pages gets lost. While the results can be reordered on the client side (the way the set of results gets selected is based on the ordering used in the generator module, it's just the order inside the resultset that gets garbled), this is an inconvenience for the consumer, especially when it is not easy to use the same ordering in different environments (e.g. sort by title, which can contain unicode characters). The API should preserve whatever sorting the generator uses.
Description
Description
Related Objects
Related Objects
Event Timeline
Comment Actions
You'll mostly be working in ApiPageSet, although the final sort might have to be called externally.
Input to ApiPageSet might be page ids, revision ids, title strings, or Title objects. ApiPageSet might normalize the input and might generate additional pages internally (e.g. when the 'redirects' parameter is used).
And the items you're being asked to sort might not correspond well to the original input items. Further, deciding what's "right" when multiple input items at different positions in the input list correspond to a single output item isn't straightforward.
Comment Actions
I can see that the generator's result set and the actual result set are in many-to-one relation when the redirects parameter is used and there are multiple redirects pointing to the same title. (Same for converttitles as well, I guess?) Is that what you mean or are there other cases in which the relationship between the generator's and the final page set is tricky?
Comment Actions
When the generator produces revids, multiple revids might map to one page. It's unlikely that a generator would produce unnormalized or duplicate titles, but not impossible.