Skip to content
← DocumentationDownload raw source

LANGUAGE V1 · FROZEN REFERENCE

Capability registry

274 results · Page 14 of 23

supabase

cron

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

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

custom schemas

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

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

custom sql

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

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

database functions

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

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

database triggers

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

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

database views

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

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

delete actions

supported — Laygent v1 implements delete actions in its supabase target.

Requirements and limitations
Id
supabase.delete_actions
Status
supported
Aliases
  • delete actions
  • supabase delete actions
  • use delete actions
  • add delete actions
  • support delete actions
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

delete behaviors

supported — Laygent v1 implements delete behaviors in its supabase target.

Requirements and limitations
Id
supabase.delete_behaviors
Status
supported
Aliases
  • delete behaviors
  • supabase delete behaviors
  • use delete behaviors
  • add delete behaviors
  • support delete behaviors
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

edge functions

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

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

email password auth

supported — Laygent v1 implements email password auth in its supabase target.

Requirements and limitations
Id
supabase.email_password_auth
Status
supported
Aliases
  • email login
  • password authentication
  • user signup
  • account login
  • email password auth
  • supabase email password auth
  • use email password auth
  • add email password auth
  • support email password auth
Evidence
fullstack.py backend parser/generator and publishing.py provisioning
Limitation
Required slots
None
Dependencies
  • supabase.backend
Conflicts
None
Defaults
Clarify when
None
Alternatives
None
supabase

embeddings

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

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

existing project configuration

supported — Laygent v1 implements existing project configuration in its supabase target.

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