[lavaturtle]

This updates the example response for the /petitions/search endpoint to reflect new fields that have been added as part of the search page redesign:

• current_page in the meta section
• categories for each petition
• activity_score for each petition

While I was here, I went through and checked that this example reflects all the current fields in the JSON. It does, except that we're not showing an example of the image field (which is only included when the petition has an image). So I added an image to one of the petitions in the example response.

[woodhull]

I approve this docs update.

Separately, and not in a way that disrupts this work, i wanted to wonder outloud if the search endpoint should be cursor paginated, but then I decided that it likely had many fewer pages and was backed by elasticsearch so this perf concern we've been fighting elsewhere in the API is potentially not relevant.

[lavaturtle]

Separately, and not in a way that disrupts this work, i wanted to wonder outloud if the search endpoint should be cursor paginated, but then I decided that it likely had many fewer pages and was backed by elasticsearch so this perf concern we've been fighting elsewhere in the API is potentially not relevant.

Hmm, interesting question! Since search results are sorted by "relevance" rather than id, id-based cursor pagination wouldn't work. But elasticsearch does have some support for pagination -- offset or cursor -- discussed here: https://www.elastic.co/docs/reference/elasticsearch/rest-apis/paginate-search-results