ix(postgrest): filter out undefined values in match method

[MichaelDeBoey]

🔍 Description

What changed?

Filter out undefined values from the query

Why was this change needed?

Closes #2167

🔄 Breaking changes

• This PR contains no breaking changes

📋 Checklist

• I have read the Contributing Guidelines
• My PR title follows the conventional commit format: <type>(<scope>): <description>
• I have run npx nx format to ensure consistent code formatting
• I have added tests for new functionality (if applicable)
• [N/A] I have updated documentation (if applicable)

Edit from @mandarini:

Note on behavior change

Previously, passing undefined values in the match() query object would result in the literal string eq.undefined being appended as a query parameter (e.g., ?column=eq.undefined). This was never valid PostgREST syntax and would produce errors or unexpected results.

With this change, undefined values are silently filtered out, matching the existing behavior in PostgrestClient.rpc(). While technically a behavior change, the previous behavior was broken and no one should be relying on eq.undefined being sent as a filter. So I am categorizing this as a fix.

[pkg-pr-new]

Open in StackBlitz

@supabase/auth-js

npm i https://pkg.pr.new/@supabase/auth-js@2169

@supabase/functions-js

npm i https://pkg.pr.new/@supabase/functions-js@2169

@supabase/postgrest-js

npm i https://pkg.pr.new/@supabase/postgrest-js@2169

@supabase/realtime-js

npm i https://pkg.pr.new/@supabase/realtime-js@2169

@supabase/storage-js

npm i https://pkg.pr.new/@supabase/storage-js@2169

@supabase/supabase-js

npm i https://pkg.pr.new/@supabase/supabase-js@2169

commit: 94b3f95