DataInput component code name
The DataInput component is referred to as `Input` in code, not `DataInput`. It should not be confused with the atomic Input component.
Supabase · Database · all subjects
out of scope
15 notes, read out of this brain and free to use. Each one was extracted from a source and is re-checked against its exam.
DataInput use case for read-only values
Input should be used for read-only values that can be copied or otherwise interacted with, as the input element is both keyboard and mouse-friendly.
DataInput sensitive value handling
Inputs with sensitive values can be both revealed and copied, but only in succession. This reduces the amount of actions on screen, thus simplifying the interface.
DataInput can be edited without revealing value
Inputs can be edited without revealing their sensitive values.
DataInput value truncation with placeholder override
You can partially truncate the value by overriding the placeholder value. A common pattern is to display a partially masked value but save the actual value in the clipboard by passing a pre-masked string as the `value` prop and overriding the `onCopy` callback to copy the real value.
DataInput password manager attributes
To prevent password managers from applying their widgets and dropdowns to the input, add the following attributes: `data-1p-ignore` for 1Password, `data-lpignore="true"` for LastPass, `data-form-type="other"` for Dashlane, and `data-bwignore` for Bitwarden.
MCP tools permissions reference table
Complete list of MCP (Model Context Protocol) tools available in Supabase with their required permissions. Tools: apply_migration (Migrations Read-write), confirm_cost (None - always available), create_branch (Development Branches Read-write OR Production Branches Read-write), create_project (Organization Projects Read-write), delete_branch (Production Branches Read-write OR Development Branches Read-write), deploy_edge_function (Edge Functions Read-write), execute_sql (Database Read), generate_typescript_types (Database Read), get_advisors (Advisors Read), get_cost (Organization Settings Read AND Projects account-wide Read), get_edge_function (Edge Functions Read), get_logs (Logs Read), get_organization (Organization Settings Read), get_project (Project Settings Read), get_project_url (Project Settings Read), get_publishable_keys (API Keys Read), get_storage_config (Storage Config Read), list_branches (Development Branches Read OR Production Branches Read), list_edge_functions (Edge Functions Read), list_extensions (Database Read), list_migrations (Migrations Read), list_organizations (Organizations Read), list_projects (Projects account-wide Read), list_storage_buckets (Storage Read), list_tables (Database Read), merge_branch (Production Branches Read-write OR Development Branches Read-write), pause_project (Project Settings Read-write), query_logs (Logs Read), rebase_branch (Production Branches Read-write OR Development Branches Read-write), reset_branch (Production Branches Read-write OR Development Branches Read-write), restore_project (Project Settings Read-write), search_docs (None - always available), update_storage_config (Storage Config Read-write).
PAT permissions for Project Settings management
Project Settings requires Read access for: Get JIT access config, Get postgres upgrade eligibility, Get postgres upgrade status, Get project, Get services health, List available restore versions, List private link associations, Preview a project transfer. Project Settings requires Read-write access for: Cancel a project restoration, Create private link association, Delete a project, Delete private link association, Delete private link association for database, Get pgsodium config, OAuth authorize project claim, Pause a project, Restart a project, Restore a project, Update a project, Update auth service config, Update JIT access config, Update pgsodium config, Upgrade postgres version.
PAT permissions for Database management
Database permission with Read access covers: Generate typescript types, Get database metadata, Get database openapi, Get postgres upgrade eligibility, Get postgres upgrade status, Get project config, Get project PgBouncer config, Read only query, Run a query. Database permission with Read-write access covers: Create login role, Delete login roles, Run a query, Upgrade postgres version.
PAT permissions for Database Config
Database Config requires Read access for: Get postgres config, Get project config. Database Config requires Read-write access for: Update database password, Update postgres config.
PAT permissions for SSL Enforcement
SSL Enforcement requires Read access for: Get project config, Get SSL enforcement config. SSL Enforcement requires Read-write access for: Update SSL enforcement config.
PAT permissions for Backups
Backups permission with Read access covers: Get backup schedule, List all backups. Backups permission with Read-write access covers: Restore PITR backup, Update backup schedule.
PAT permissions for Migrations
Migrations requires Read access for: Get a migration, List migration history. Migrations requires Read-write access for: Apply a migration, Patch a migration, Rollback migrations, Upsert a migration.
PAT permissions for Edge Functions and Edge Function Secrets
Edge Functions requires Read access for: Get a function, Get a function body, List all functions. Edge Functions requires Read-write access for: Bulk update functions, Create a function, Delete a function, Deploy a function, Update a function. Edge Function Secrets requires Read access for: List all secrets. Edge Function Secrets requires Read-write access for: Bulk create secrets, Bulk delete secrets.
Get project config API dependencies
The Get project config endpoint requires Read access to: Database Config, Database, SSL Enforcement, Network Restrictions, Auth Config, Data API Config, Realtime Config, and Storage Config.