In the pattern search API, use the client locale when querying

[iandunn]

See #223 / #224

Pulls locale from post meta, see #229

Pre-launch

• Use locale param when querying patterns (WP_Query)
• Add e2e test -- https://meta.trac.wordpress.org/changeset/11082/

Post-launch

• After, Search description instead of post content #28 is done, switch to ES to mitigate performance issues w/ meta queries. Do for front-end too, like Theme: Query results show translated patterns side by side. #273
• Prioritize search based on locale (ala Learn), rather than simple include/exclude. Do for the API, but also for the front end (related Theme: Query results show translated patterns side by side. #273)

[dd32]

d75ca62 causes a bit of a shortcoming, in that patterns without a translation become inaccessible.

Instead, I think we need to prioritise translated patterns but not skip not-localised.

[iandunn]

Do you mean that requests for es_MX patterns won't include en_US "parent" patterns that don't have a es_MX "child/translated" variant/fork yet?

That seems good enough for launch, since all the "core/featured" patterns will be translated.

We might want to wait until after #28 too, since ES might make that prioritization easier. On the other hand, Learn already does that kind of sorting w/ WP_Query, so we could just copy that 🤔

[iandunn]

Removing this from the milestone since the pre-launch tasks are done.

[ryelle]

It looks like all the linked PRs have been merged, so I'm going to close this issue.