Why does Flutterflow's integration with Supabase only allow access to the public schema of the database?

Supabase allows you to make more schemas accessible via the API. However, Flutterflow integration with Supabase only reads the public schema. A complex software project needs to organize its tables into different schemas. Why does Supabase only read the public schema?