Instead of mutating the shared client object when dealing with table names, headers, and param fields, we instead push them down to the transport layer and have it collate them into a fresh request object instead. This allows re-use of the Supabase client for multiple requests.
Instead of mutating the shared client object when dealing with table names, headers, and param fields, we instead push them down to the transport layer and have it collate them into a fresh request object instead. This allows re-use of the Supabase client for multiple requests.
Fixes #12