feat: use undefined as bottom value instead of null

[soedirgo]

BREAKING CHANGE: use undefined as bottom value instead of null

[steve-chavez]

Why is this needed?

[soedirgo]

Here's the discussion on this: supabase/supabase-js#244. Basically it doesn't make sense to treat null as a sentinel value when undefined is already implied for optional fields. E.g. null is redundant in count?: null | 'exact' | ... because it also accepts undefined anyway.

Note that this change only applies to function args etc. - it doesn't modify PostgREST's response at all. That way it's more consistent in that the absence of value in the JS part is undefined while null is only ever used to represent a Postgres null, e.g. for the .is() filter.

[github-actions]

🎉 This PR is included in version 1.0.0-next.1 🎉

The release is available on:

• GitHub release
• npm package (@next dist-tag)

Your semantic-release bot 📦🚀