Types and generic from<T>

[AlbinoGeek]

Synopsis

The types in @supabase/supabase-js such as User don't quite line up with .from<T>(string) don't quite line up with their usage, such as .eq('email_confirmed_at', null).

Description

So, say we use a type like User from @supabase/supabase-js

export interface User {
  id: string
  app_metadata: {
    provider?: string
    [key: string]: any
  }
  user_metadata: {
    [key: string]: any
  }
  aud: string
  confirmation_sent_at?: string
  recovery_sent_at?: string
  email_change_sent_at?: string
  new_email?: string
  invited_at?: string
  action_link?: string
  email?: string
  phone?: string
  created_at: string
  confirmed_at?: string
  email_confirmed_at?: string
  phone_confirmed_at?: string
  last_sign_in_at?: string
  role?: string
  updated_at?: string
  identities?: UserIdentity[]
}

Then we write a query using one of the "possibly undefined" fields:

    // return a list of users who were invited but not yet confirmed
    const { data, error } = await supabaseSERVER
      .from<User>('auth.users')
      .select('id, email, invited_at')
      .eq('email_confirmed_at', null)

Now, unfortunately, this fails ESLint, because null isn't a valid value for email_confirmed_at.

The same thing happens when using Update.

Possible Solutions

Maybe eq and other comparators should accept T | null as it's value, so that null is always a valid value?

---

This is an idea versus an issue, because I'm not sold on this being the solution. I'd rather someone who uses supabase more than me weigh in on the implications of such a change.

Disclaimer: Yes, I'm aware User might not be the best example, since auth is a private collection, but this applies to all types that use undefined as their default value, which includes types I make.