Add support for database types on different schemas.

[dts]

This plumbs through a config-set schema name to the types system.

Types of changes

• Bug fix (a non-breaking change which fixes an issue)
• New feature (a non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Description

Currently, types do not correctly reflect overridden schemas. This PR allows that schema to be plumbed through reasonably.

Checklist:

• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have added tests to cover my changes (if not applicable, please state why)
  Not sure what tests apply here.

[netlify]

👷 Deploy request for n3-supabase pending review.

Visit the deploys page to approve it

Name	Link
🔨 Latest commit	b6e0bea

[IsraelOrtuno]

There's a problem with this at the moment as it seems that the types imports (here) in the composables are being wiped out when running the build command:

dist/runtime/composables/useSupabaseClient.d.ts

import type { SupabaseClient } from '@supabase/supabase-js';
export declare const useSupabaseClient: <T = unknown, S extends string & keyof T = Schema>() => SupabaseClient<T, S>;

#383 (comment)

For me this only works when running in the playground folder as the build is prepared using --stub, which doesn't remove any import.

If you want to reproduce just run pnpm run build and check dist/runtime/composables/useSupabaseClient.d.ts. You will see that import type { Database, Schema } from '#build/types/supabase-database' will be gone.

I am still figuring out how to fix this.

[larbish]

@dts @IsraelOrtuno Could you have a check now that #404 has been merged?

[IsraelOrtuno]

This fixed the issues with my PR so I would say it should work now @dts