Filtering for list endpoints

[david-crespo]

We will need to able to filter list endpoints. Presumably, because these are GET endpoints, we will do this filtering through query parameters.

Example table design with filtering (Figma)

It seems to me we will want something like the following in Nexus:

• For each paginated endpoint, specify the fields clients can filter on and their schemas
• Expose the above specifications in the OpenAPI spec as query parameters so clients know how to use them

Corners to cut

• Start with only name and timestamp fields

Open questions

• How do we do text matching on names
  • Presumably we want to keep it simple and start with something like WHERE name ILIKE '<query>%' and worry about getting fancy later

[davepacheco]

I know we've talked a bunch about the scalability problems with this. (Basically, how do you avoid this turning into a table scan?) I can't remember if we've written this down somewhere.