class
Analyzer::Specification::Supabase
- Analyzer::Specification::Supabase
- Analyzer
- Reference
- Object
Overview
Supabase serves PostgREST at /rest/v1/, exposing one resource per
table or view in an exposed schema.
Two things make this differ from the other CRUD analyzers:
- There is no
/rest/v1/<table>/<id>path. PostgREST addresses rows with a filter (?id=eq.1), so every verb lands on the collection URL and the column names are valid query keys. - Only exposed schemas are reachable. Supabase migrations routinely
create tables in
auth,storageandextensions, none of which PostgREST serves.
Included Modules
Defined in:
analyzer/analyzers/specification/supabase.crConstant Summary
-
DEFAULT_EXPOSED_SCHEMAS =
{"public"} -
PostgREST's default exposed schema. Supabase adds
graphql_public, which carries no user tables. -
INTERNAL_SCHEMAS =
{"auth", "storage", "extensions", "graphql", "graphql_public", "realtime", "vault", "net", "cron", "pgsodium", "pgbouncer", "supabase_functions", "supabase_migrations", "information_schema", "pg_catalog"} -
Internal schemas that appear in migrations but are never served.
-
MAX_FILTER_PARAMS =
25 -
REST_PREFIX =
"/rest/v1" -
TAG_SOURCE =
"supabase_analyzer"