CLI not exposing custom schema despite listing in config.toml
I've been attempting to setup my local workflow, however I've been running into issues with my custom schemas not being exposed. I've tried quite a few resets, starts & stops, and even trying a rename of the schema with no success. The schema works completely fine remotely, I'm just having this issue running from the local configuration.
I've attached a photo from the local version of the studio and the config.toml in case it highlights anything. As you can see the RLS policies are being loaded just fine, it seems to just be the exposure issue.
If anyone has any ideas on how to resolve this or if I'm just missing a step please let me know!
I'm running on Windows 11 with Supabase CLI v2.54.11.
I've attached a photo from the local version of the studio and the config.toml in case it highlights anything. As you can see the RLS policies are being loaded just fine, it seems to just be the exposure issue.
If anyone has any ideas on how to resolve this or if I'm just missing a step please let me know!
I'm running on Windows 11 with Supabase CLI v2.54.11.
