Not sure if it's been mentioned before but the filter docs are a little confusing when the examples are so granular -- is it possible to provide a tiny table for context, even if it's the same one traveling sticky down the side of the page that all the examples can match up against? For example

const { data, error } = await supabase
  .from('cities')
  .select('name, country_id')
  .eq('name', 'The Shire')

can be inferred decently well. From the table cities, select the name and country_id where the name eq(uals) The Shire but this is contains()

.contains('main_exports', ['oil'])

and containedBy()

.containedBy('main_exports', ['cars', 'food', 'machine'])

and the pages don't even say what they do, so if I tried to read it, I might think "main exports column contains oil" and then "main export columns...is contained by cars? Cars, food and machine are contained by main_exports?" Is it just a semantic swap? In the PostgreSQL docs they seem really deliberate about "this is how the lefthand bit relates to the righthand bit" which most people maybe don't need to be told but for those that do, even a single sentence could make it incontrovertibly clear. And a baby demo table would let them draw the conclusion on their own. Might even be fun to have a demo table playground to run the functions against to really bring it home.

Yeah, that sounds good. Could you open an issue on https://github.com/supabase/supabase/issues/?

I appreciate the consideration. I tried to clean it up and make it a bit more concise. Thank you for your time!