LANGUAGE V1 · FROZEN REFERENCE
Capability registry
274 results · Page 18 of 23
supabasesign out
supported — Laygent v1 implements sign out in its supabase target.
Requirements and limitations
- Id
- supabase.sign_out
- Status
- supported
- Aliases
- sign out
- supabase sign out
- use sign out
- add sign out
- support sign out
- Evidence
- fullstack.py backend parser/generator and publishing.py provisioning
- Limitation
- Required slots
- None
- Dependencies
- None
- Conflicts
- None
- Clarify when
- None
- Alternatives
- None
supabasesigned urls
unsupported — Laygent v1 does not implement signed urls in its supabase target.
Requirements and limitations
- Id
- supabase.signed_urls
- Status
- unsupported
- Aliases
- signed urls
- supabase signed urls
- use signed urls
- add signed urls
- support signed urls
- Evidence
- Limitation
- Laygent v1 does not implement signed urls in its supabase target.
- Required slots
- None
- Dependencies
- None
- Conflicts
- None
- Clarify when
- None
- Alternatives
- None
supabasesocial oauth
unsupported — Laygent v1 does not implement social oauth in its supabase target.
Requirements and limitations
- Id
- supabase.social_oauth
- Status
- unsupported
- Aliases
- social oauth
- supabase social oauth
- use social oauth
- add social oauth
- support social oauth
- Evidence
- Limitation
- Laygent v1 does not implement social oauth in its supabase target.
- Required slots
- None
- Dependencies
- None
- Conflicts
- None
- Clarify when
- None
- Alternatives
- None
supabasestorage buckets
supported — Laygent v1 implements storage buckets in its supabase target.
Requirements and limitations
- Id
- supabase.storage_buckets
- Status
- supported
- Aliases
- storage bucket
- file bucket
- private files
- public uploads
- storage buckets
- supabase storage buckets
- use storage buckets
- add storage buckets
- support storage buckets
- Evidence
- fullstack.py backend parser/generator and publishing.py provisioning
- Limitation
- Conflicts
- None
- Clarify when
- file visibility is not inferable
- Alternatives
- None
supabasestorage downloads
unsupported — Laygent v1 does not implement storage downloads in its supabase target.
Requirements and limitations
- Id
- supabase.storage_downloads
- Status
- unsupported
- Aliases
- storage downloads
- supabase storage downloads
- use storage downloads
- add storage downloads
- support storage downloads
- Evidence
- Limitation
- Laygent v1 does not implement storage downloads in its supabase target.
- Required slots
- None
- Dependencies
- None
- Conflicts
- None
- Clarify when
- None
- Alternatives
- None
supabasestorage listing
unsupported — Laygent v1 does not implement storage listing in its supabase target.
Requirements and limitations
- Id
- supabase.storage_listing
- Status
- unsupported
- Aliases
- storage listing
- supabase storage listing
- use storage listing
- add storage listing
- support storage listing
- Evidence
- Limitation
- Laygent v1 does not implement storage listing in its supabase target.
- Required slots
- None
- Dependencies
- None
- Conflicts
- None
- Clarify when
- None
- Alternatives
- None
supabasestorage move copy
unsupported — Laygent v1 does not implement storage move copy in its supabase target.
Requirements and limitations
- Id
- supabase.storage_move_copy
- Status
- unsupported
- Aliases
- storage move copy
- supabase storage move copy
- use storage move copy
- add storage move copy
- support storage move copy
- Evidence
- Limitation
- Laygent v1 does not implement storage move copy in its supabase target.
- Required slots
- None
- Dependencies
- None
- Conflicts
- None
- Clarify when
- None
- Alternatives
- None
supabasestorage owner policies
supported — Laygent v1 implements storage owner policies in its supabase target.
Requirements and limitations
- Id
- supabase.storage_owner_policies
- Status
- supported
- Aliases
- storage owner policies
- supabase storage owner policies
- use storage owner policies
- add storage owner policies
- support storage owner policies
- Evidence
- fullstack.py backend parser/generator and publishing.py provisioning
- Limitation
- Required slots
- None
- Dependencies
- None
- Conflicts
- None
- Clarify when
- None
- Alternatives
- None
supabasetables
supported — Laygent v1 implements tables in its supabase target.
Requirements and limitations
- Id
- supabase.tables
- Status
- supported
- Aliases
- tables
- supabase tables
- use tables
- add tables
- support tables
- Evidence
- fullstack.py backend parser/generator and publishing.py provisioning
- Limitation
- Conflicts
- None
- Clarify when
- None
- Alternatives
- None
supabasetyped function fields
supported — Laygent v1 implements typed function fields in its supabase target.
Requirements and limitations
- Id
- supabase.typed_function_fields
- Status
- supported
- Aliases
- typed function fields
- supabase typed function fields
- use typed function fields
- add typed function fields
- support typed function fields
- Evidence
- fullstack.py backend parser/generator and publishing.py provisioning
- Limitation
- Required slots
- None
- Dependencies
- None
- Conflicts
- None
- Clarify when
- None
- Alternatives
- None
supabaseupdate forms
supported — Laygent v1 implements update forms in its supabase target.
Requirements and limitations
- Id
- supabase.update_forms
- Status
- supported
- Aliases
- update forms
- supabase update forms
- use update forms
- add update forms
- support update forms
- Evidence
- fullstack.py backend parser/generator and publishing.py provisioning
- Limitation
- Required slots
- None
- Dependencies
- None
- Conflicts
- None
- Clarify when
- None
- Alternatives
- None
supabasevectors
unsupported — Laygent v1 does not implement vectors in its supabase target.
Requirements and limitations
- Id
- supabase.vectors
- Status
- unsupported
- Aliases
- vector search
- embeddings
- pgvector
- semantic search
- vectors
- supabase vectors
- use vectors
- add vectors
- support vectors
- Evidence
- Limitation
- Laygent v1 does not implement vectors in its supabase target.
- Required slots
- None
- Dependencies
- None
- Conflicts
- None
- Clarify when
- None
- Alternatives
- None