Skip to content
← DocumentationDownload raw source

LANGUAGE V1 · FROZEN REFERENCE

Capability registry

274 results · Page 15 of 23

supabase

explicit grants

supported — Laygent v1 implements explicit grants in its supabase target.

Requirements and limitations
Id
supabase.explicit_grants
Status
supported
Aliases
  • explicit grants
  • supabase explicit grants
  • use explicit grants
  • add explicit grants
  • support explicit grants
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

extensions

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

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

external api calls

partial — Edge Functions can forward POST JSON to one secret URL; arbitrary methods, headers and response transforms are absent.

Requirements and limitations
Id
supabase.external_api_calls
Status
partial
Aliases
  • external api calls
  • supabase external api calls
  • use external api calls
  • add external api calls
  • support external api calls
Evidence
Limitation
Edge Functions can forward POST JSON to one secret URL; arbitrary methods, headers and response transforms are absent.
Required slots
None
Dependencies
None
Conflicts
None
Defaults
Clarify when
None
Alternatives
None
supabase

file upload

supported — Laygent v1 implements file upload in its supabase target.

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

full text search

unsupported — Laygent v1 does not implement full text search in its supabase target.

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

function invocation

supported — Laygent v1 implements function invocation in its supabase target.

Requirements and limitations
Id
supabase.function_invocation
Status
supported
Aliases
  • function invocation
  • supabase function invocation
  • use function invocation
  • add function invocation
  • support function invocation
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

graphql

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

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

image transforms

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

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

indexes

supported — Laygent v1 implements indexes in its supabase target.

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

insert forms

supported — Laygent v1 implements insert forms in its supabase target.

Requirements and limitations
Id
supabase.insert_forms
Status
supported
Aliases
  • insert forms
  • supabase insert forms
  • use insert forms
  • add insert forms
  • support insert forms
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

joins

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

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

json function response

supported — Laygent v1 implements json function response in its supabase target.

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