[wp-trac] [WordPress Trac] #52590: Consider increasing the limit of the perPage argument in paginated requests.

[WordPress Trac]

#52590: Consider increasing the limit of the perPage argument in paginated
requests.
-------------------------+-----------------------------
 Reporter:  youknowriad  |      Owner:  (none)
     Type:  enhancement  |     Status:  new
 Priority:  normal       |  Milestone:  Awaiting Review
Component:  REST API     |    Version:
 Severity:  normal       |   Keywords:
  Focuses:  rest-api     |
-------------------------+-----------------------------
 In some situations where we fetch a small number of fields, clients might
 want to fetch a big number of items  at once. For instance in Gutenberg,
 while selecting parent pages or selecting authors, ideally we should be
 able to fetch  more than 100 elements at once.

 I understand that the current limits  are there to avoid memory issues but
 clients can make informed decisions by fetching a small number of fields
 instead to avoid said memory issues. Most issues seems to happen when you
 fetch the "content" field in the posts end point.

 After some discussion on slack. it was suggested that we could consider
 increasing that limit depending on a the requested fields.

 Another option that was shared was to rely on the "embed" context.

 https://wordpress.slack.com/archives/C02RQC26G/p1613382691029000

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/52590>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform