Skip to content
← DocumentationDownload raw source

LANGUAGE V1 · FROZEN REFERENCE

Capability registry

274 results · Page 13 of 23

supabase

advanced filters

unsupported — Laygent v1 does not implement advanced filters in its supabase target.

Requirements and limitations
Id
supabase.advanced_filters
Status
unsupported
Aliases
  • advanced filters
  • supabase advanced filters
  • use advanced filters
  • add advanced filters
  • support advanced filters
Evidence
Limitation
Laygent v1 does not implement advanced filters in its supabase target.
Required slots
None
Dependencies
None
Conflicts
None
Defaults
Clarify when
None
Alternatives
None
supabase

aggregation

unsupported — Laygent v1 does not implement aggregation in its supabase target.

Requirements and limitations
Id
supabase.aggregation
Status
unsupported
Aliases
  • aggregation
  • supabase aggregation
  • use aggregation
  • add aggregation
  • support aggregation
Evidence
Limitation
Laygent v1 does not implement aggregation in its supabase target.
Required slots
None
Dependencies
None
Conflicts
None
Defaults
Clarify when
None
Alternatives
None
supabase

anonymous auth

unsupported — Laygent v1 does not implement anonymous auth in its supabase target.

Requirements and limitations
Id
supabase.anonymous_auth
Status
unsupported
Aliases
  • anonymous auth
  • supabase anonymous auth
  • use anonymous auth
  • add anonymous auth
  • support anonymous auth
Evidence
Limitation
Laygent v1 does not implement anonymous auth in its supabase target.
Required slots
None
Dependencies
None
Conflicts
None
Defaults
Clarify when
None
Alternatives
None
supabase

api key discovery

supported — Laygent v1 implements api key discovery in its supabase target.

Requirements and limitations
Id
supabase.api_key_discovery
Status
supported
Aliases
  • api key discovery
  • supabase api key discovery
  • use api key discovery
  • add api key discovery
  • support api key discovery
Evidence
fullstack.py backend parser/generator and publishing.py provisioning
Limitation
Required slots
None
Dependencies
None
Conflicts
None
Defaults
Clarify when
None
Alternatives
None
supabase

auth redirect

supported — Laygent v1 implements auth redirect in its supabase target.

Requirements and limitations
Id
supabase.auth_redirect
Status
supported
Aliases
  • auth redirect
  • supabase auth redirect
  • use auth redirect
  • add auth redirect
  • support auth redirect
Evidence
fullstack.py backend parser/generator and publishing.py provisioning
Limitation
Required slots
None
Dependencies
None
Conflicts
None
Defaults
Clarify when
None
Alternatives
None
supabase

authenticated functions

supported — Laygent v1 implements authenticated functions in its supabase target.

Requirements and limitations
Id
supabase.authenticated_functions
Status
supported
Aliases
  • authenticated functions
  • supabase authenticated functions
  • use authenticated functions
  • add authenticated functions
  • support authenticated functions
Evidence
fullstack.py backend parser/generator and publishing.py provisioning
Limitation
Required slots
None
Dependencies
None
Conflicts
None
Defaults
Clarify when
None
Alternatives
None
supabase

backend

supported — Laygent v1 implements backend in its supabase target.

Requirements and limitations
Id
supabase.backend
Status
supported
Aliases
  • backend
  • supabase backend
  • use backend
  • add backend
  • support backend
Evidence
fullstack.py backend parser/generator and publishing.py provisioning
Limitation
Required slots
None
Dependencies
None
Conflicts
None
Defaults
Clarify when
None
Alternatives
None
supabase

background jobs

unsupported — Laygent v1 does not implement background jobs in its supabase target.

Requirements and limitations
Id
supabase.background_jobs
Status
unsupported
Aliases
  • background jobs
  • supabase background jobs
  • use background jobs
  • add background jobs
  • support background jobs
Evidence
Limitation
Laygent v1 does not implement background jobs in its supabase target.
Required slots
None
Dependencies
None
Conflicts
None
Defaults
Clarify when
None
Alternatives
None
supabase

backups

unsupported — Laygent v1 does not implement backups in its supabase target.

Requirements and limitations
Id
supabase.backups
Status
unsupported
Aliases
  • backups
  • supabase backups
  • use backups
  • add backups
  • support backups
Evidence
Limitation
Laygent v1 does not implement backups in its supabase target.
Required slots
None
Dependencies
None
Conflicts
None
Defaults
Clarify when
None
Alternatives
None
supabase

branching

unsupported — Laygent v1 does not implement branching in its supabase target.

Requirements and limitations
Id
supabase.branching
Status
unsupported
Aliases
  • branching
  • supabase branching
  • use branching
  • add branching
  • support branching
Evidence
Limitation
Laygent v1 does not implement branching in its supabase target.
Required slots
None
Dependencies
None
Conflicts
None
Defaults
Clarify when
None
Alternatives
None
supabase

column constraints

supported — Laygent v1 implements column constraints in its supabase target.

Requirements and limitations
Id
supabase.column_constraints
Status
supported
Aliases
  • column constraints
  • supabase column constraints
  • use column constraints
  • add column constraints
  • support column constraints
Evidence
fullstack.py backend parser/generator and publishing.py provisioning
Limitation
Required slots
None
Dependencies
None
Conflicts
None
Defaults
Clarify when
None
Alternatives
None
supabase

column types

supported — Laygent v1 implements column types in its supabase target.

Requirements and limitations
Id
supabase.column_types
Status
supported
Aliases
  • column types
  • supabase column types
  • use column types
  • add column types
  • support column types
Evidence
fullstack.py backend parser/generator and publishing.py provisioning
Limitation
Required slots
None
Dependencies
None
Conflicts
None
Defaults
Clarify when
None
Alternatives
None