Skip to content

LANGUAGE V1 · FROZEN REFERENCE

Capability registry

274 results · Page 16 of 23

supabase

logs advisors

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

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

magic links

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

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

migration application

supported — Laygent v1 implements migration application in its supabase target.

Requirements and limitations
Id
supabase.migration_application
Status
supported
Aliases
  • migration application
  • supabase migration application
  • use migration application
  • add migration application
  • support migration application
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

multifactor auth

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

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

otp auth

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

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

owner policies

supported — Laygent v1 implements owner policies in its supabase target.

Requirements and limitations
Id
supabase.owner_policies
Status
supported
Aliases
  • own rows
  • user owned records
  • only their data
  • row ownership
  • owner policies
  • supabase owner policies
  • use owner policies
  • add owner policies
  • support owner policies
Evidence
fullstack.py backend parser/generator and publishing.py provisioning
Limitation
Required slots
  • owner_column
Dependencies
  • supabase.rls
  • supabase.email_password_auth
Conflicts
None
Defaults
Owner column
user_id
Clarify when
None
Alternatives
None
supabase

pagination

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

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

password reset

supported — Laygent v1 implements password reset in its supabase target.

Requirements and limitations
Id
supabase.password_reset
Status
supported
Aliases
  • password reset
  • supabase password reset
  • use password reset
  • add password reset
  • support password reset
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

phone auth

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

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

project provisioning

supported — Laygent v1 implements project provisioning in its supabase target.

Requirements and limitations
Id
supabase.project_provisioning
Status
supported
Aliases
  • project provisioning
  • supabase project provisioning
  • use project provisioning
  • add project provisioning
  • support project provisioning
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

protected pages

supported — Laygent v1 implements protected pages in its supabase target.

Requirements and limitations
Id
supabase.protected_pages
Status
supported
Aliases
  • protected pages
  • supabase protected pages
  • use protected pages
  • add protected pages
  • support protected pages
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

public read policy

supported — Laygent v1 implements public read policy in its supabase target.

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