-
-
-
-
-
-
-
- Supabase
-
-
- {children}
-
-
@@ -106,6 +106,7 @@ export function ResultsList({
))}
+ {infiniteLoadingObserverRef && }
)
}
diff --git a/apps/studio/components/interfaces/App/CommandMenu/ContextSearchResults.tsx b/apps/studio/components/interfaces/App/CommandMenu/ContextSearchResults.tsx
index 80701e4458b..205f34fa940 100644
--- a/apps/studio/components/interfaces/App/CommandMenu/ContextSearchResults.tsx
+++ b/apps/studio/components/interfaces/App/CommandMenu/ContextSearchResults.tsx
@@ -45,6 +45,7 @@ const StorageSearchResults = dynamic(
interface ContextSearchResultsProps {
context: SearchContextValue
query: string
+ debouncedFilterString: string
}
const CONTEXT_CONFIG: Record<
@@ -77,13 +78,17 @@ const CONTEXT_CONFIG: Record<
},
}
-export function ContextSearchResults({ context, query }: ContextSearchResultsProps) {
+export function ContextSearchResults({
+ context,
+ query,
+ debouncedFilterString,
+}: ContextSearchResultsProps) {
const config = CONTEXT_CONFIG[context]
if (context === 'database-tables') {
return (
)
}
diff --git a/apps/studio/components/interfaces/Database/Publications/PublicationsTableItem.tsx b/apps/studio/components/interfaces/Database/Publications/PublicationsTableItem.tsx
index df2e4f2685f..5ef3ea67a85 100644
--- a/apps/studio/components/interfaces/Database/Publications/PublicationsTableItem.tsx
+++ b/apps/studio/components/interfaces/Database/Publications/PublicationsTableItem.tsx
@@ -75,7 +75,6 @@ export const PublicationsTableItem = ({
return (
{table.name}
- {table.schema}
{table.comment}
diff --git a/apps/studio/components/interfaces/Database/Publications/PublicationsTables.tsx b/apps/studio/components/interfaces/Database/Publications/PublicationsTables.tsx
index 00390fd5d37..60b969f3564 100644
--- a/apps/studio/components/interfaces/Database/Publications/PublicationsTables.tsx
+++ b/apps/studio/components/interfaces/Database/Publications/PublicationsTables.tsx
@@ -10,9 +10,12 @@ import { PublicationTablesSkeleton } from './PublicationSkeleton'
import { PublicationsTableItem } from './PublicationsTableItem'
import { AlertError } from '@/components/ui/AlertError'
import { NoSearchResults } from '@/components/ui/NoSearchResults'
+import SchemaSelector from '@/components/ui/SchemaSelector'
+import { Shortcut } from '@/components/ui/Shortcut'
import { useDatabasePublicationsQuery } from '@/data/database-publications/database-publications-query'
import { useTablesQuery } from '@/data/tables/tables-query'
import { useAsyncCheckPermissions } from '@/hooks/misc/useCheckPermissions'
+import { useQuerySchemaState } from '@/hooks/misc/useSchemaQueryState'
import { useSelectedProjectQuery } from '@/hooks/misc/useSelectedProject'
import { onSearchInputEscape } from '@/lib/keyboard'
import { SHORTCUT_IDS } from '@/state/shortcuts/registry'
@@ -21,7 +24,10 @@ import { useShortcut } from '@/state/shortcuts/useShortcut'
export const PublicationsTables = () => {
const { id } = useParams()
const { data: project } = useSelectedProjectQuery()
+ const { selectedSchema, setSelectedSchema } = useQuerySchemaState()
+
const [filterString, setFilterString] = useState('')
+ const [schemaSelectorOpen, setSchemaSelectorOpen] = useState(false)
const searchInputRef = useRef(null)
const { can: canUpdatePublications, isLoading: isLoadingPermissions } = useAsyncCheckPermissions(
@@ -53,6 +59,7 @@ export const PublicationsTables = () => {
} = useTablesQuery({
projectRef: project?.ref,
connectionString: project?.connectionString,
+ schema: selectedSchema,
})
const tables = useMemo(() => {
@@ -63,7 +70,23 @@ export const PublicationsTables = () => {
return (
<>
-
- handleBarClick(v as UsageApiCounts, 'realtime')}
- customDateFormat={datetimeFormat}
- highlightedValue={sumBy(charts, 'total_realtime_requests')}
- />
-
-
-
-
-
- )
-}
-export default ProjectUsage
-
-const PanelHeader = (props: any) => {
- const Tag = props?.href ? Link : 'div'
- return (
-
-
)
}
diff --git a/apps/studio/components/interfaces/App/CommandMenu/TableSearchResults.tsx b/apps/studio/components/interfaces/App/CommandMenu/TableSearchResults.tsx
index 66266fcd47b..6861f0ca1dd 100644
--- a/apps/studio/components/interfaces/App/CommandMenu/TableSearchResults.tsx
+++ b/apps/studio/components/interfaces/App/CommandMenu/TableSearchResults.tsx
@@ -1,8 +1,7 @@
-'use client'
-
+import { useIntersectionObserver } from '@uidotdev/usehooks'
import { useParams } from 'common'
import { Database, Loader2 } from 'lucide-react'
-import { useMemo } from 'react'
+import { useEffect, useMemo } from 'react'
import {
EmptyState,
@@ -10,55 +9,44 @@ import {
SkeletonResults,
type SearchResult,
} from './ContextSearchResults.shared'
-import { useTablesQuery } from '@/data/tables/tables-query'
+import { useInfiniteTablesQuery } from '@/data/tables/tables-query'
import { useSelectedProjectQuery } from '@/hooks/misc/useSelectedProject'
interface TableSearchResultsProps {
- query: string
+ debouncedFilterString: string
}
-export function TableSearchResults({ query }: TableSearchResultsProps) {
+export function TableSearchResults({ debouncedFilterString }: TableSearchResultsProps) {
const { ref: projectRef } = useParams()
const { data: project } = useSelectedProjectQuery()
- const trimmedQuery = query.trim()
+ const [sentinelRef, sentinelEntry] = useIntersectionObserver({
+ threshold: 0,
+ rootMargin: '200px 0px 200px 0px',
+ })
const {
- data: tables,
- isLoading: isLoadingTables,
+ data: tablesData,
+ isSuccess,
isError: isErrorTables,
- } = useTablesQuery(
- {
- projectRef: project?.ref,
- connectionString: project?.connectionString,
- includeColumns: false,
- sortByProperty: 'name',
- },
- {
- enabled: !!project?.ref,
- }
- )
+ isPending: isLoadingTables,
+ hasNextPage: hasNextTablesPage,
+ isFetchingNextPage: isFetchingNextTablesPage,
+ fetchNextPage: fetchNextTablesPage,
+ } = useInfiniteTablesQuery({
+ projectRef: project?.ref,
+ connectionString: project?.connectionString,
+ includeColumns: false,
+ pageSize: 50,
+ nameFilter: debouncedFilterString,
+ })
+
+ const tables = useMemo(() => tablesData?.pages.flat() ?? [], [tablesData])
const tableResults: SearchResult[] = useMemo(() => {
if (!tables) return []
- const filtered = trimmedQuery
- ? tables.filter((table) => {
- const searchLower = trimmedQuery.toLowerCase()
- const tableName = table.name?.toLowerCase() || ''
- const schemaName = table.schema?.toLowerCase() || ''
- const fullName = `${schemaName}.${tableName}`
-
- return (
- tableName.includes(searchLower) ||
- schemaName.includes(searchLower) ||
- fullName.includes(searchLower)
- )
- })
- : tables
-
- // Limit results for performance
- return filtered.slice(0, 20).map((table) => {
+ return tables.map((table) => {
const displayName =
table.schema && table.schema !== 'public'
? `${table.schema}.${table.name}`
@@ -76,79 +64,71 @@ export function TableSearchResults({ query }: TableSearchResultsProps) {
description,
}
})
- }, [tables, trimmedQuery])
+ }, [tables])
const totalTables = tables?.length ?? 0
- const renderFooter = () => (
-
-
- )
-
- if (isLoadingTables) {
- return (
-
- {isLoadingTables ? (
-
-
-
-
- )
- }
-
- if (isErrorTables) {
- return (
-
-
- {renderFooter()}
-
-
- )
- }
-
- if (tableResults.length === 0) {
- return (
-
-
- {renderFooter()}
-
-
- Failed to load tables
-
-
- )
- }
+ useEffect(() => {
+ if (
+ sentinelEntry?.isIntersecting &&
+ hasNextTablesPage &&
+ !isFetchingNextTablesPage &&
+ isSuccess
+ ) {
+ fetchNextTablesPage()
+ }
+ }, [
+ isSuccess,
+ sentinelEntry?.isIntersecting,
+ hasNextTablesPage,
+ isFetchingNextTablesPage,
+ fetchNextTablesPage,
+ ])
return (
-
- {renderFooter()}
-
- {
- const table = tables?.find((t) => String(t.id) === result.id)
- if (!table || !projectRef) return `/project/${projectRef}/editor` as `/${string}`
+ {isLoadingTables ? (
+ {
+ const table = tables?.find((t) => String(t.id) === result.id)
+ if (!table || !projectRef) return `/project/${projectRef}/editor` as `/${string}`
- const schemaParam = table.schema ? `?schema=${table.schema}` : ''
- return `/project/${projectRef}/editor/${table.id}${schemaParam}` as `/${string}`
- }}
- className="pb-9"
- />
+ const schemaParam = table.schema ? `?schema=${table.schema}` : ''
+ return `/project/${projectRef}/editor/${table.id}${schemaParam}` as `/${string}`
+ }}
+ infiniteLoadingObserverRef={sentinelRef}
+ className="pb-9"
+ />
+
- {renderFooter()}
+
+ ) : tableResults.length === 0 ? (
+ Failed to load tables
+
+
+
+ )}
+ {isLoadingTables ? (
+
+
+
+
@@ -45,6 +55,12 @@ export const ProductMenuItem = ({
)
+ // When data necessary to check whether an item should be disabled is not yet available, override the styles to avoid
+ // showing the disabled state just for a moment
+ if (isLoading) {
+ return
hasIcon?: boolean
+ isLoading?: boolean
} & VariantProps
>(
(
@@ -546,6 +554,7 @@ const SidebarMenuButton = React.forwardRef<
variant = 'default',
size = 'default',
hasIcon = true,
+ isLoading = false,
tooltip,
className,
...props
@@ -570,7 +579,7 @@ const SidebarMenuButton = React.forwardRef<
data-active={isActive}
data-has-icon={hasIcon}
tabIndex={computedTabIndex}
- className={cn(sidebarMenuButtonVariants({ variant, size, hasIcon }), className)}
+ className={cn(sidebarMenuButtonVariants({ variant, size, hasIcon, isLoading }), className)}
{...props}
/>
)
From 726e226f666a9da7e03be6592df5af0814c72ca6 Mon Sep 17 00:00:00 2001
From: "supabase-supabase-autofixer[bot]"
<248690971+supabase-supabase-autofixer[bot]@users.noreply.github.com>
Date: Tue, 16 Jun 2026 09:34:58 +0000
Subject: [PATCH 011/488] [bot] Sync from supabase/troubleshooting (#46971)
This PR syncs the latest troubleshooting guides from the
supabase/troubleshooting repository.
---------
Co-authored-by: github-docs-bot
Co-authored-by: Chris Chinchilla
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
---
...t-exist-when-using-or-operators-46ff23.mdx | 46 +++++++++++++++++++
1 file changed, 46 insertions(+)
create mode 100644 apps/docs/content/troubleshooting/postgrest-error-400-column-example_tableexample_column-does-not-exist-when-using-or-operators-46ff23.mdx
diff --git a/apps/docs/content/troubleshooting/postgrest-error-400-column-example_tableexample_column-does-not-exist-when-using-or-operators-46ff23.mdx b/apps/docs/content/troubleshooting/postgrest-error-400-column-example_tableexample_column-does-not-exist-when-using-or-operators-46ff23.mdx
new file mode 100644
index 00000000000..09c1c7314bf
--- /dev/null
+++ b/apps/docs/content/troubleshooting/postgrest-error-400-column-example_tableexample_column-does-not-exist-when-using-or-operators-46ff23.mdx
@@ -0,0 +1,46 @@
+---
+title = "PostgREST error: 400 'column example_table.example_column does not exist' when using OR operators"
+date_created = "2026-06-15T04:04:26+00:00"
+topics = [ "platform", "api" ]
+keywords = [ "postgrest", "column does not exist" ]
+[[errors]]
+http_status_code = 400
+message = "column example_table.example_column does not exist"
+
+---
+
+If you receive a `400` error with the message `column example_table.example_column does not exist` only on mutation requests (`PATCH`, `POST`, `DELETE`) — while `SELECT` queries on the same column work fine — this is a known bug in PostgREST versions before 14.4 ([issue #3707](https://github.com/PostgREST/postgrest/issues/3707)).
+
+## Root cause
+
+The bug is triggered when an `or()` filter is included in a mutation request. PostgREST incorrectly applies the OR filter's column resolution logic to the mutation plan, causing it to fail to locate columns that exist and are otherwise accessible.
+
+## How to confirm
+
+1. **Reproduce the asymmetry** — run the same filter as a `GET` request. If it succeeds but the `PATCH`/`POST`/`DELETE` fails with the same column reference, the bug is the likely cause.
+2. **Check your PostgREST version** — go to [Project Settings > Infrastructure](/dashboard/project/_/settings/infrastructure) and note the PostgreSQL version. PostgREST 14.1 and earlier are affected; 14.4+ includes the fix.
+3. **Check Postgres logs** — if you have logging enabled, you should see `column "example_column" does not exist` errors correlating with the timestamps of the failed mutation requests.
+
+## Resolution
+
+### Option 1: Upgrade (permanent fix)
+
+Navigate to [Project Settings > Infrastructure](/dashboard/project/_/settings/infrastructure) and upgrade to the latest Postgres version. This automatically upgrades PostgREST to 14.5+, where the bug is resolved.
+
+### Option 2: Query workaround (immediate)
+
+Explicitly include the column referenced in the error in the `select` parameter of your mutation request. This forces PostgREST to resolve the column correctly during the mutation plan.
+
+For example, if your request looks like:
+
+```
+PATCH /rest/v1/example_table?or=(example_column.eq.value1,example_column.eq.value2)
+```
+
+Add `select=` with the affected column:
+
+```
+PATCH /rest/v1/example_table?or=(example_column.eq.value1,example_column.eq.value2)&select=id,example_column
+```
+
+This workaround applies per-request and does not require any schema changes or infrastructure modifications.
From b4a15bb0c897de87bbd7c775fe47608a05cc93b5 Mon Sep 17 00:00:00 2001
From: Guillaume Faas <59444272+Tr00d@users.noreply.github.com>
Date: Tue, 16 Jun 2026 12:18:56 +0200
Subject: [PATCH 012/488] chores(docs): add Guillaume Faas to humans.txt
(#46968)
Contributed through a fork as I'm not yet in the GitHub Org
## Summary by CodeRabbit
* **Chores**
* Updated the public team roster by adding a new team member.
---
apps/docs/public/humans.txt | 1 +
1 file changed, 1 insertion(+)
diff --git a/apps/docs/public/humans.txt b/apps/docs/public/humans.txt
index 9324b96b44e..a2765dcef91 100644
--- a/apps/docs/public/humans.txt
+++ b/apps/docs/public/humans.txt
@@ -111,6 +111,7 @@ Greg Marzouka
Greg P
Greg Richardson
Gregor Vand
+Guillaume Faas
Guilherme Souza
Hanefi Önaldı
Hannah Bowers
From 30ee68964fb4df072df899906524ffc9be7b8ffe Mon Sep 17 00:00:00 2001
From: Jeremias Menichelli
Date: Tue, 16 Jun 2026 12:47:19 +0200
Subject: [PATCH 013/488] chore:new AST based script supporting current
markdown for LLMs (#46949)
---
.../internals/generate-guides-markdown.ts | 323 ++++++++----------
.../internals/markdown-schema/Admonition.ts | 13 +
apps/docs/internals/markdown-schema/Link.ts | 12 +
apps/docs/internals/markdown-schema/Panel.ts | 3 +
.../internals/markdown-schema/StepHike.ts | 16 +
.../internals/markdown-schema/TabPanel.ts | 9 +
6 files changed, 187 insertions(+), 189 deletions(-)
create mode 100644 apps/docs/internals/markdown-schema/Admonition.ts
create mode 100644 apps/docs/internals/markdown-schema/Link.ts
create mode 100644 apps/docs/internals/markdown-schema/Panel.ts
create mode 100644 apps/docs/internals/markdown-schema/StepHike.ts
create mode 100644 apps/docs/internals/markdown-schema/TabPanel.ts
diff --git a/apps/docs/internals/generate-guides-markdown.ts b/apps/docs/internals/generate-guides-markdown.ts
index 6758ba073ac..856ec2c79c7 100644
--- a/apps/docs/internals/generate-guides-markdown.ts
+++ b/apps/docs/internals/generate-guides-markdown.ts
@@ -1,198 +1,160 @@
-import fs from 'node:fs'
+import fs from 'node:fs/promises'
import path from 'node:path'
import { globby } from 'globby'
import matter from 'gray-matter'
+import type { Content, Parent, Root } from 'mdast'
+import { fromMarkdown } from 'mdast-util-from-markdown'
+import { gfmFromMarkdown, gfmToMarkdown } from 'mdast-util-gfm'
+import { mdxFromMarkdown, mdxToMarkdown } from 'mdast-util-mdx'
+import type { MdxJsxFlowElement, MdxJsxTextElement } from 'mdast-util-mdx-jsx'
+import { toMarkdown } from 'mdast-util-to-markdown'
+import { gfm } from 'micromark-extension-gfm'
+import { mdxjs } from 'micromark-extension-mdxjs'
-import { getInternalLinkBaseUrl, prefixInternalLinks, withDocsBasePath } from './internal-links'
+import { getInternalLinkBaseUrl, prefixInternalLinks } from './internal-links'
+import { Link } from './markdown-schema/Link'
+import { Panel } from './markdown-schema/Panel'
+import { StepHike } from './markdown-schema/StepHike'
+import { TabPanel } from './markdown-schema/TabPanel'
+import { Admonition } from './markdown-schema/Admonition'
const PARTIALS_DIR = path.join(process.cwd(), 'content', '_partials')
+type JsxNode = MdxJsxFlowElement | MdxJsxTextElement
+type Props = Record
+
/**
- * Reads <$Partial path="..." /> tags and replaces them with the file contents.
- * Recurses to handle nested partials.
+ * A handler converts a single MDX component into a markdown string. It receives
+ * the component's props, the already-serialized markdown of its children, and
+ * the raw AST node (escape hatch for handlers that need to inspect structure).
+ *
+ * Any component not in the schema is treated as `({ children }) => children`,
+ * i.e. the wrapper is dropped and its children are kept as-is.
*/
-async function inlinePartials(content: string): Promise {
- const partialRegex = /<\$Partial\s+path="([^"]+)"[^/]*\/>/g
- const matches = [...content.matchAll(partialRegex)]
- for (const [fullMatch, partialPath] of matches) {
- try {
- const raw = await fs.promises.readFile(path.join(PARTIALS_DIR, partialPath), 'utf8')
- const { content: partialBody } = matter(raw)
- const inlined = await inlinePartials(partialBody)
- content = content.replace(fullMatch, inlined)
- } catch {
- content = content.replace(fullMatch, '')
- }
+type ComponentHandler = (ctx: { props: Props; children: string; node: JsxNode }) => string
+type ComponentSchema = Record
+
+const PARSE_OPTIONS = {
+ extensions: [mdxjs(), gfm()],
+ mdastExtensions: [mdxFromMarkdown(), gfmFromMarkdown()],
+}
+const SERIALIZE_OPTIONS = {
+ extensions: [mdxToMarkdown(), gfmToMarkdown()],
+ bullet: '-' as const,
+ listItemIndent: 'one' as const,
+}
+
+const parseMdx = (source: string): Root => fromMarkdown(source, PARSE_OPTIONS)
+const serializeMdx = (tree: Parent): string => toMarkdown(tree as Root, SERIALIZE_OPTIONS)
+
+const defaultHandler: ComponentHandler = ({ children }) => children
+
+const isJsx = (n: Content): n is JsxNode =>
+ n.type === 'mdxJsxFlowElement' || n.type === 'mdxJsxTextElement'
+
+function propsFrom(node: JsxNode): Props {
+ const props: Props = {}
+ for (const attr of node.attributes) {
+ if (attr.type !== 'mdxJsxAttribute') continue
+ if (attr.value == null) props[attr.name] = true
+ else if (typeof attr.value === 'string') props[attr.name] = attr.value
+ else props[attr.name] = attr.value.value
}
- return content
-}
-
-/** Remove the minimum common leading whitespace from all non-empty lines. */
-function dedentBlock(text: string): string {
- const lines = text.split('\n')
- const nonEmpty = lines.filter((l) => /\S/.test(l))
- if (!nonEmpty.length) return text
- const minIndent = Math.min(...nonEmpty.map((l) => (l.match(/^([ \t]*)/) ?? ['', ''])[1].length))
- if (!minIndent) return text
- return lines.map((l) => l.slice(minIndent)).join('\n')
+ return props
}
/**
- * Converts StepHikeCompact components to markdown ordered lists.
- * Each step becomes a numbered item: the title (from Details) is bolded on the item
- * line, and the full step body (Details + Code) is dedented and appended below.
- * Remaining JSX tags inside the body are later stripped by stripJsxTags.
+ * Replaces every `<$Partial path="..." />` in the tree with the parsed AST of
+ * the referenced file. Recurses so partials may include other partials.
*/
-function convertStepHike(content: string): string {
- return content.replace(/([\s\S]*?)<\/StepHikeCompact>/g, (_, body) => {
- const items: string[] = []
- const stepRe = /]*>([\s\S]*?)<\/StepHikeCompact\.Step>/g
- let stepNum = 1
- let m: RegExpExecArray | null
- while ((m = stepRe.exec(body)) !== null) {
- const stepBody = m[1]
- const titleMatch = stepBody.match(/]+title="([^"]*)"/)
- const title = titleMatch ? titleMatch[1] : ''
- // Dedent the entire step body so nested JSX indentation is removed.
- // Remaining component tags (Details, Code, Admonition…) are stripped later.
- const inner = dedentBlock(stepBody).trim()
- const item = title ? `${stepNum}. **${title}**\n\n${inner}` : `${stepNum}. ${inner}`
- items.push(item)
- stepNum++
+async function inlinePartials(parent: Parent): Promise {
+ const next: Content[] = []
+ for (const child of parent.children as Content[]) {
+ if (isJsx(child) && child.name === '$Partial') {
+ const partialPath = String(propsFrom(child).path ?? '')
+ try {
+ const raw = await fs.readFile(path.join(PARTIALS_DIR, partialPath), 'utf8')
+ const subtree = parseMdx(matter(raw).content)
+ await inlinePartials(subtree)
+ next.push(...(subtree.children as Content[]))
+ } catch {
+ // missing or broken partials are silently dropped
+ }
+ continue
}
- return items.join('\n\n')
- })
-}
-
-/**
- * Extracts a `title` prop value from a JSX opening-tag's attribute text.
- * Supports `title="..."`, `title='...'`, and `title={... }` forms.
- * For JSX titles, strips inline tags and collapses whitespace so the text
- * content remains.
- */
-function extractTitleAttr(attrs: string): string | null {
- const strMatch = attrs.match(/\btitle=(?:"([^"]+)"|'([^']+)')/)
- if (strMatch) return strMatch[1] ?? strMatch[2]
-
- const exprIdx = attrs.indexOf('title={')
- if (exprIdx === -1) return null
-
- let i = exprIdx + 'title={'.length
- const inner: string[] = []
- let depth = 1
- while (i < attrs.length && depth > 0) {
- const ch = attrs[i]
- if (ch === '{') depth++
- else if (ch === '}') {
- depth--
- if (depth === 0) break
- }
- inner.push(ch)
- i++
+ if ('children' in child) await inlinePartials(child as Parent)
+ next.push(child)
}
- return inner
- .join('')
- .replace(/<[^>]+>/g, ' ')
- .replace(/\s+/g, ' ')
- .trim()
+ parent.children = next as Parent['children']
}
/**
- * Converts `desc`
- * blocks into markdown bullet lines: `- [title](href). description`. Without
- * this, the rendered output keeps prop syntax (className, passHref, etc.) since
- * stripping JSX tags discards inner text from props but leaves panel children
- * floating without context. Applied to all guides so resource-card grids render
- * consistently in the markdown view.
+ * Walks the tree bottom-up. For each JSX element, runs its schema handler (or
+ * the default) and replaces the node with an `html` node holding the result.
+ * The `html` type passes through `mdast-util-to-markdown` verbatim, so whatever
+ * markdown the handler returns lands in the final output unchanged.
*/
-function convertLinkPanels(content: string): string {
- return content.replace(/([\s\S]*?)<\/Link>/g, (full, linkAttrs, body) => {
- const hrefMatch = linkAttrs.match(/\bhref="([^"]+)"/)
- if (!hrefMatch) return full
- const href = withDocsBasePath(hrefMatch[1])
-
- const panelOpen = body.match(/<(GlassPanel|IconPanel)\b/)
- if (!panelOpen) return full
- const panelName = panelOpen[1]
- const panelStart = panelOpen.index ?? 0
-
- // Walk past the opening tag, respecting JSX expression braces so attribute
- // values like `title={...}` don't terminate parsing early.
- let i = panelStart + panelOpen[0].length
- let depth = 0
- while (i < body.length) {
- const ch = body[i]
- if (ch === '{') depth++
- else if (ch === '}') depth--
- else if (ch === '>' && depth === 0) break
- i++
+function applySchema(parent: Parent, schema: ComponentSchema): void {
+ for (const child of parent.children as Content[]) {
+ if ('children' in child) applySchema(child as Parent, schema)
+ }
+ const next: Content[] = []
+ for (const child of parent.children as Content[]) {
+ if (
+ child.type === 'mdxFlowExpression' ||
+ child.type === 'mdxTextExpression' ||
+ child.type === 'mdxjsEsm'
+ ) {
+ continue
}
- if (i >= body.length) return full
-
- const panelAttrs = body.slice(panelStart + panelOpen[0].length, i)
- const closingTag = ``
- const closeIdx = body.indexOf(closingTag, i)
- if (closeIdx === -1) return full
-
- const title = extractTitleAttr(panelAttrs)
- if (!title) return full
-
- const description = body
- .slice(i + 1, closeIdx)
- .replace(/<[^>]+>/g, ' ')
- .replace(/\s+/g, ' ')
- .trim()
-
- return `- [${title}](${href})${description ? `. ${description}` : ''}`
- })
+ if (isJsx(child)) {
+ const handler = schema[child.name ?? ''] ?? defaultHandler
+ const children = serializeMdx({
+ type: 'root',
+ children: child.children as Root['children'],
+ }).trim()
+ const value = handler({ props: propsFrom(child), children, node: child })
+ next.push({ type: 'html', value } as Content)
+ continue
+ }
+ next.push(child)
+ }
+ parent.children = next as Parent['children']
}
/**
- * Strips JSX component tags (capitalized names, dot-notation, or $-prefixed)
- * while keeping their inner content. Also strips wrapper div and a elements.
- * Removes MDX JSX comment blocks. Strips unnecessary leading indentation from
- * non-code-block lines.
+ * Per-component overrides. Each handler receives `{ props, children, node }`
+ * and returns the markdown string that should replace the JSX element. Any
+ * component not listed is unwrapped (children are kept, wrapper is dropped).
*/
-function stripJsxTags(content: string): string {
- // Remove MDX/JSX comments {/* ... */}
- content = content.replace(/\{\/\*[\s\S]*?\*\/\}/g, '')
+const SCHEMA: ComponentSchema = {
+ Admonition,
+ Link,
+ GlassPanel: Panel,
+ IconPanel: Panel,
+ ...StepHike,
+ TabPanel,
+}
- // Remove self-closing JSX components: {
+ const raw = await fs.readFile(filePath, 'utf8')
+ const { content, data } = matter(raw)
- // Remove opening JSX component tags (possibly multi-line):
- content = content.replace(/<[\$A-Z][\w.]*(?:\s[^>]*)?\s*>/gs, '')
+ const tree = parseMdx(content)
+ await inlinePartials(tree)
+ applySchema(tree, SCHEMA)
+ const body = prefixInternalLinks(serializeMdx(tree), linkBaseUrl)
- // Remove closing JSX component tags:
- content = content.replace(/<\/[\$A-Z][\w.]*>/g, '')
+ const headerParts: string[] = []
+ if (data.title) headerParts.push(`# ${data.title}`)
+ if (data.subtitle) headerParts.push(String(data.subtitle))
+ // Add description only when differs from subtitle.
+ if (data.description && String(data.description) !== String(data.subtitle))
+ headerParts.push(String(data.description))
- // Remove wrapper div and a elements used structurally in MDX (carry JSX props
- // like className which are not valid HTML; inner content such as img is preserved)
- content = content.replace(/]*)?\s*>/g, '')
- content = content.replace(/<\/div>/g, '')
- content = content.replace(/]*)?\s*>/g, '')
- content = content.replace(/<\/a>/g, '')
+ const header = headerParts.join('\n\n')
- // Split on fenced code blocks to handle prose and code separately.
- // For prose (even segments): strip leading whitespace (removes JSX nesting indent).
- // For code blocks (odd segments): dedent the body to remove JSX nesting indent while
- // preserving relative code structure, then normalize the closing fence.
- const segments = content.split(/(```[\s\S]*?```)/g)
- content = segments
- .map((seg, i) => {
- if (i % 2 === 0) return seg.replace(/^[ \t]+/gm, '')
- return seg.replace(
- /^(```[^\n]*\n)([\s\S]*?)(\n[ \t]*```)$/,
- (_, open, body) => open + dedentBlock(body) + '\n```'
- )
- })
- .join('')
-
- // Collapse lines that are only whitespace to empty lines, then deduplicate blank lines
- content = content.replace(/^[^\S\n]+$/gm, '')
- content = content.replace(/\n{3,}/g, '\n\n').trim()
-
- return content
+ return header ? `${header}\n\n${body}` : body
}
async function generate() {
@@ -202,47 +164,30 @@ async function generate() {
await Promise.all(
files.map(async (filePath) => {
+ // content/guides/ai/vector-columns.mdx → public/markdown/guides/ai/vector-columns.md
+ // Placing under public/markdown/ ensures the file is served at /docs/guides/...
+ // matching the URL of the rendered page.
const outPath = filePath
.replace(/^content\/guides\//, 'public/markdown/guides/')
.replace(/\.mdx$/, '.md')
let output: string
try {
- const raw = await fs.promises.readFile(filePath, 'utf8')
- const { content: rawContent, data } = matter(raw)
-
- const withPartials = await inlinePartials(rawContent)
- const withSteps = convertStepHike(withPartials)
- const withLinks = convertLinkPanels(withSteps)
- const stripped = stripJsxTags(withLinks)
- const processed = prefixInternalLinks(stripped, linkBaseUrl)
-
- const header = [
- data.title ? `# ${data.title}` : '',
- data.subtitle || data.description ? `\n${data.subtitle ?? data.description}` : '',
- ]
- .filter(Boolean)
- .join('\n')
-
- output = header ? `${header}\n\n${processed}` : processed
+ output = await generateOne(filePath, linkBaseUrl)
} catch (err) {
warnings++
console.warn(
`[warn] Failed to process ${filePath}: ${err instanceof Error ? err.message : err}`
)
- // Fall back to raw file content so the route still serves something
try {
- output = await fs.promises.readFile(filePath, 'utf8')
+ output = await fs.readFile(filePath, 'utf8')
} catch {
output = ``
}
}
- // content/guides/ai/vector-columns.mdx → public/markdown/guides/ai/vector-columns.md
- // Placing under public/markdown/ ensures the file is served at /docs/guides/...
- // matching the exact URL of the rendered page.
- await fs.promises.mkdir(path.dirname(outPath), { recursive: true })
- await fs.promises.writeFile(outPath, output)
+ await fs.mkdir(path.dirname(outPath), { recursive: true })
+ await fs.writeFile(outPath, output)
})
)
diff --git a/apps/docs/internals/markdown-schema/Admonition.ts b/apps/docs/internals/markdown-schema/Admonition.ts
new file mode 100644
index 00000000000..06d90d5875b
--- /dev/null
+++ b/apps/docs/internals/markdown-schema/Admonition.ts
@@ -0,0 +1,13 @@
+export const Admonition = ({
+ props,
+ children,
+}: {
+ props: Record
+ children: string
+}): string => {
+ const type = props.type ? String(props.type) : 'note'
+ return `${capitalize(type)}: ${children}`
+}
+
+const capitalize = (s: T) =>
+ (s[0].toUpperCase() + s.slice(1)) as Capitalize
diff --git a/apps/docs/internals/markdown-schema/Link.ts b/apps/docs/internals/markdown-schema/Link.ts
new file mode 100644
index 00000000000..3d0888c956a
--- /dev/null
+++ b/apps/docs/internals/markdown-schema/Link.ts
@@ -0,0 +1,12 @@
+import { withDocsBasePath } from '../internal-links'
+
+export const Link = ({
+ props,
+ children,
+}: {
+ props: Record
+ children: string
+}): string => {
+ const href = withDocsBasePath(String(props.href ?? ''))
+ return `[${children}](${href})`
+}
diff --git a/apps/docs/internals/markdown-schema/Panel.ts b/apps/docs/internals/markdown-schema/Panel.ts
new file mode 100644
index 00000000000..2962e24d403
--- /dev/null
+++ b/apps/docs/internals/markdown-schema/Panel.ts
@@ -0,0 +1,3 @@
+export const Panel = ({ props }: { props: Record }): string => {
+ return String(props.title)
+}
diff --git a/apps/docs/internals/markdown-schema/StepHike.ts b/apps/docs/internals/markdown-schema/StepHike.ts
new file mode 100644
index 00000000000..89435a7e054
--- /dev/null
+++ b/apps/docs/internals/markdown-schema/StepHike.ts
@@ -0,0 +1,16 @@
+type Props = Record
+type Ctx = { props: Props; children: string }
+
+const Step = ({ props, children }: Ctx): string => {
+ const step = String(props.step ?? '').trim()
+ return step ? `${step}. ${children}` : children
+}
+
+const Details = ({ props, children }: Ctx): string => {
+ return props.title ? `**${String(props.title).trim()}**\n\n${children}` : children
+}
+
+export const StepHike = {
+ 'StepHikeCompact.Step': Step,
+ 'StepHikeCompact.Details': Details,
+}
diff --git a/apps/docs/internals/markdown-schema/TabPanel.ts b/apps/docs/internals/markdown-schema/TabPanel.ts
new file mode 100644
index 00000000000..3ffbd801e69
--- /dev/null
+++ b/apps/docs/internals/markdown-schema/TabPanel.ts
@@ -0,0 +1,9 @@
+export const TabPanel = ({
+ props,
+ children,
+}: {
+ props: Record
+ children: string
+}): string => {
+ return props.label ? `**${String(props.label)}**\n\n${children}` : children
+}
From a10bc9a88ae0ce1b19c77fd811e4fb7abc61426c Mon Sep 17 00:00:00 2001
From: Jordi Enric <37541088+jordienr@users.noreply.github.com>
Date: Tue, 16 Jun 2026 12:50:52 +0200
Subject: [PATCH 014/488] feat(unified-logs): compact toggle banner and
ArrowDown selects first log (#46812)
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Visual cleanup of the Logs sidebar (unified logs):
- Restyle the "Go back to old logs" and "Try Unified Logs" banners as
full-bleed bordered strips (no card), with an icon-only switch-back
button and a tooltip
- Add a "Beta" badge next to the "Logs" sidebar title
- Rename the product from "Logs & Analytics" to "Logs"
## Summary by CodeRabbit
* **New Features**
* Added Unified Logs banner with “Try Unified Logs” and “More
information” actions, plus a “Go back to old logs” utility layout.
* Show a **“Beta”** badge for Unified Logs eligibility.
* **UX Updates**
* Updated the Logs experience to consistently display under the
**“Logs”** product layout.
* **Tests / Documentation**
* Updated end-to-end checks and examples to expect the **“Logs”**
heading text exactly.
---------
Co-authored-by: Claude Opus 4.8
Co-authored-by: kemal
---
.../UnifiedLogs/UnifiedLogsBanner.tsx | 63 +++++++++++++++++++
.../layouts/LogsLayout/LogsLayout.tsx | 10 ++-
.../layouts/LogsLayout/LogsSidebarMenuV2.tsx | 37 +++--------
.../components/ui/DataTable/FilterSideBar.tsx | 38 ++++-------
e2e/studio/README.md | 2 +-
e2e/studio/features/logs.spec.ts | 6 +-
6 files changed, 93 insertions(+), 63 deletions(-)
create mode 100644 apps/studio/components/interfaces/UnifiedLogs/UnifiedLogsBanner.tsx
diff --git a/apps/studio/components/interfaces/UnifiedLogs/UnifiedLogsBanner.tsx b/apps/studio/components/interfaces/UnifiedLogs/UnifiedLogsBanner.tsx
new file mode 100644
index 00000000000..15cc4bcba18
--- /dev/null
+++ b/apps/studio/components/interfaces/UnifiedLogs/UnifiedLogsBanner.tsx
@@ -0,0 +1,63 @@
+import { CircleHelpIcon, Undo2 } from 'lucide-react'
+import { Button, cn } from 'ui'
+
+import { ButtonTooltip } from '@/components/ui/ButtonTooltip'
+
+interface UnifiedLogsBannerProps {
+ variant: 'promo' | 'utility'
+ onEnable?: () => void
+ onMoreInfo?: () => void
+ onSwitchBack?: () => void
+ className?: string
+}
+
+export function UnifiedLogsBanner({
+ variant,
+ onEnable,
+ onMoreInfo,
+ onSwitchBack,
+ className,
+}: UnifiedLogsBannerProps) {
+ const stripClassName = cn(
+ 'flex items-center justify-between gap-3 border-b border-border px-4 py-3',
+ className
+ )
+
+ if (variant === 'utility') {
+ return (
+ ) =>
if (!logsEnabled) {
return (
-
+
)
@@ -33,14 +33,12 @@ const LogsLayout = ({ title, children }: PropsWithChildren) =>
if (!canUseLogsExplorer) {
if (isLoading) {
- return (
-
+
)
@@ -49,7 +47,7 @@ const LogsLayout = ({ title, children }: PropsWithChildren) =>
return (
New}
- actions={
- <>
-
- {
+ enableUnifiedLogs()
+ router.push(`/project/${ref}/logs`)
+ }}
+ onMoreInfo={() => selectFeaturePreview('supabase-ui-preview-unified-logs')}
/>
)}
diff --git a/apps/studio/components/ui/DataTable/FilterSideBar.tsx b/apps/studio/components/ui/DataTable/FilterSideBar.tsx
index e4297f5a50b..6ed57d3e663 100644
--- a/apps/studio/components/ui/DataTable/FilterSideBar.tsx
+++ b/apps/studio/components/ui/DataTable/FilterSideBar.tsx
@@ -1,10 +1,9 @@
-import { LOCAL_STORAGE_KEYS, useParams } from 'common'
+import { useParams } from 'common'
import Link from 'next/link'
import { useRouter } from 'next/router'
import React, { useEffect, type ReactNode } from 'react'
-import { Button, cn, ResizablePanel, usePanelRef } from 'ui'
+import { Badge, Button, cn, ResizablePanel, usePanelRef } from 'ui'
-import { FeaturePreviewBadge } from '../FeaturePreviewBadge'
import { FeaturePreviewSidebarPanel } from '../FeaturePreviewSidebarPanel'
import { DateRangeDisabled } from './DataTable.types'
import { DataTableFilterControls } from './DataTableFilters/DataTableFilterControls'
@@ -12,6 +11,7 @@ import { DataTableResetButton } from './DataTableResetButton'
import { useDataTable } from './providers/DataTableProvider'
import { useUnifiedLogsPreview } from '@/components/interfaces/App/FeaturePreview/FeaturePreviewContext'
import { LOG_DRAIN_TYPES } from '@/components/interfaces/LogDrains/LogDrains.constants'
+import { UnifiedLogsBanner } from '@/components/interfaces/UnifiedLogs/UnifiedLogsBanner'
interface FilterSideBarProps {
isFilterBarOpen: boolean
@@ -30,11 +30,7 @@ export function FilterSideBar({
const { ref } = useParams()
const { table } = useDataTable()
- const {
- disable: disableUnifiedLogs,
- isEligible: isUnifiedLogsEligible,
- isEnabled: isUnifiedLogsEnabled,
- } = useUnifiedLogsPreview()
+ const { disable: disableUnifiedLogs, isEligible: isUnifiedLogsEligible } = useUnifiedLogsPreview()
const handleGoBackToOldLogs = () => {
disableUnifiedLogs()
@@ -70,29 +66,19 @@ export function FilterSideBar({
>
+ {isUnifiedLogsEligible && (
+
- handleBarClick(v as UsageApiCounts, 'storage')}
- customDateFormat={datetimeFormat}
- highlightedValue={sumBy(charts, 'total_storage_requests')}
- />
-
-
-
- )}
-
-
-
-
- }
- title="Realtime"
- />
-
-
+ setSchemaSelectorOpen(true)}
+ side="bottom"
+ tooltipOpen={schemaSelectorOpen ? false : undefined}
+ >
+
{
Name
- Schema
Description
{/*
We've disabled All tables toggle for publications.
@@ -106,7 +128,7 @@ export const PublicationsTables = () => {
{isError && (
-
+
@@ -114,7 +136,7 @@ export const PublicationsTables = () => {
{!isLoading && !isLoadingPermissions && tables.length === 0 && (
-
+
{
))
) : (
-
+
)
} else {
return (
- The selected publication with ID {id} cannot be found
Head back to the list of publications to select one from there
diff --git a/apps/studio/components/interfaces/Database/Triggers/TriggerSheet.tsx b/apps/studio/components/interfaces/Database/Triggers/TriggerSheet.tsx
index 63d9499303f..35a1c109877 100644
--- a/apps/studio/components/interfaces/Database/Triggers/TriggerSheet.tsx
+++ b/apps/studio/components/interfaces/Database/Triggers/TriggerSheet.tsx
@@ -39,6 +39,7 @@ import FormBoxEmpty from '@/components/ui/FormBoxEmpty'
import { useDatabaseTriggerCreateMutation } from '@/data/database-triggers/database-trigger-create-mutation'
import { useDatabaseTriggerUpdateMutation } from '@/data/database-triggers/database-trigger-update-mutation'
import { useTablesQuery } from '@/data/tables/tables-query'
+import { useQuerySchemaState } from '@/hooks/misc/useSchemaQueryState'
import { useSelectedProjectQuery } from '@/hooks/misc/useSelectedProject'
import { useConfirmOnClose } from '@/hooks/ui/useConfirmOnClose'
import { useProtectedSchemas } from '@/hooks/useProtectedSchemas'
@@ -89,6 +90,7 @@ export const TriggerSheet = ({
onClose,
}: TriggerSheetProps) => {
const { data: project } = useSelectedProjectQuery()
+ const { selectedSchema } = useQuerySchemaState()
const [showFunctionSelector, setShowFunctionSelector] = useState(false)
@@ -118,6 +120,7 @@ export const TriggerSheet = ({
const { data = [], isSuccess: isSuccessTables } = useTablesQuery({
projectRef: project?.ref,
connectionString: project?.connectionString,
+ schema: selectedSchema,
})
const { data: protectedSchemas, isSuccess: isSuccessProtectedSchemas } = useProtectedSchemas()
const isSuccess = isSuccessTables && isSuccessProtectedSchemas
diff --git a/apps/studio/components/interfaces/Database/Triggers/TriggersList/TriggersList.tsx b/apps/studio/components/interfaces/Database/Triggers/TriggersList/TriggersList.tsx
index 5386a44f8e4..c47e1b89520 100644
--- a/apps/studio/components/interfaces/Database/Triggers/TriggersList/TriggersList.tsx
+++ b/apps/studio/components/interfaces/Database/Triggers/TriggersList/TriggersList.tsx
@@ -76,6 +76,7 @@ export const TriggersList = () => {
const { data = [] } = useTablesQuery({
projectRef: project?.ref,
connectionString: project?.connectionString,
+ schema: selectedSchema,
})
const hasTables =
data.filter((a) => !protectedSchemas.find((s) => s.name === a.schema)).length > 0
diff --git a/apps/studio/components/interfaces/TableGridEditor/SidePanelEditor/SidePanelEditor.tsx b/apps/studio/components/interfaces/TableGridEditor/SidePanelEditor/SidePanelEditor.tsx
index f8f08a40881..42d782b88ec 100644
--- a/apps/studio/components/interfaces/TableGridEditor/SidePanelEditor/SidePanelEditor.tsx
+++ b/apps/studio/components/interfaces/TableGridEditor/SidePanelEditor/SidePanelEditor.tsx
@@ -437,7 +437,7 @@ export const SidePanelEditor = ({
}),
queryClient.invalidateQueries({ queryKey: entityTypeKeys.list(project?.ref) }),
queryClient.invalidateQueries({
- queryKey: tableKeys.list(project?.ref, selectedTable?.schema, includeColumns),
+ queryKey: tableKeys.list(project?.ref, selectedTable?.schema, { includeColumns }),
}),
queryClient.invalidateQueries({
queryKey: tableKeys.infiniteListPrefix(project?.ref, selectedTable?.schema),
@@ -508,7 +508,7 @@ export const SidePanelEditor = ({
// Switch it to individual tables via an array of strings
// Refer to PublicationStore for more information about this
const publicTables = await queryClient.fetchQuery({
- queryKey: tableKeys.list(project.ref, 'public', includeColumns),
+ queryKey: tableKeys.list(project.ref, 'public', { includeColumns }),
queryFn: ({ signal }) =>
getTables(
{
@@ -646,10 +646,10 @@ export const SidePanelEditor = ({
.map(([, data]) => data?.pages?.[0]?.data?.count)
.find((count) => typeof count === 'number') ??
queryClient.getQueryData
+ No tables found based on your search
+
- Cannot authorize this request because the URL is missing the following parameter
- {isPlural ? 's' : ''}: {missingParameters.join(', ')}.
-
- If you followed a link here, please check the link and try again.
-
+
+
+ )}
)}
+ {isFetchingNextTablesPage ? (
+
+
+ |
|
## To test
Please do a visual check on `http://localhost:8082/authorize` (no
`auth_id` or other parameters).
## Summary by CodeRabbit
* **Bug Fixes**
* Improved the UI and copy shown when the authorization link is missing.
* Updated behavior to show an explicit error screen when authorization
requester data is unavailable.
* **New Features**
* Added a loading state for the authorization page while router
parameters are initializing.
* **Tests**
* Updated component expectations for the missing authorization and
“unable to load” scenarios.
* Added a page test to verify the loading message when the router is not
ready.
---------
Co-authored-by: Cursor
+
+
)
}
diff --git a/apps/studio/components/interfaces/ApiAuthorization/ApiAuthorization.Valid.tsx b/apps/studio/components/interfaces/ApiAuthorization/ApiAuthorization.Valid.tsx
index cb85776418a..507b06fa481 100644
--- a/apps/studio/components/interfaces/ApiAuthorization/ApiAuthorization.Valid.tsx
+++ b/apps/studio/components/interfaces/ApiAuthorization/ApiAuthorization.Valid.tsx
@@ -193,7 +193,9 @@ export function ApiAuthorizationValidScreen({
? buildStudioPageTitle({ section: `Authorize ${effectiveRequester.name}`, brand: 'Supabase' })
: undefined
- if (!effectiveRequester) return null
+ if (!effectiveRequester) {
+ return
## Solution
Check whether the required data is loading and override the styles so
that the links are still disabled to avoid errors but appear as normal.
## How to test
- Open the project setting page
- Check the styles of the sidebar items carefully while it load (might
require to refresh a few times to be sure)
## Summary by CodeRabbit
## Release Notes
* **New Features**
* Navigation buttons, menu items, and settings menus now display loading
states while project data is being fetched, providing visual feedback
and preventing interaction during data loading operations.
---
apps/studio/components/interfaces/Sidebar.tsx | 21 ++++++++++++++++---
.../SettingsMenu.utils.tsx | 11 +++++++++-
.../ui/ProductMenu/ProductMenu.types.ts | 1 +
.../ui/ProductMenu/ProductMenuItem.tsx | 18 +++++++++++++++-
.../ui/src/components/shadcn/ui/sidebar.tsx | 11 +++++++++-
5 files changed, 56 insertions(+), 6 deletions(-)
diff --git a/apps/studio/components/interfaces/Sidebar.tsx b/apps/studio/components/interfaces/Sidebar.tsx
index 4db35a2cb05..e2695958b08 100644
--- a/apps/studio/components/interfaces/Sidebar.tsx
+++ b/apps/studio/components/interfaces/Sidebar.tsx
@@ -159,6 +159,7 @@ export function SideBarNavLink({
route,
active,
onClick,
+ isLoading,
...props
}: {
route: Route
@@ -183,6 +184,7 @@ export function SideBarNavLink({
const buttonProps = {
disabled: route.disabled,
isActive: active,
+ isLoading,
className: cn('text-sm', sidebarBehaviour === 'open' ? 'px-2!' : ''),
size: 'default' as const,
onClick: onClick,
@@ -237,7 +239,7 @@ const ActiveDot = ({ hasErrors, hasWarnings }: { hasErrors: boolean; hasWarnings
const ProjectLinks = () => {
const router = useRouter()
const { ref } = useParams()
- const { data: project } = useSelectedProjectQuery()
+ const { data: project, isPending: isProjectPending } = useSelectedProjectQuery()
const { securityLints, errorLints } = useLints()
const showReports = useIsFeatureEnabled('reports:all')
const showLogs = useIsFeatureEnabled('logs:all')
@@ -295,6 +297,7 @@ const ProjectLinks = () => {
key={`tools-routes-${i}`}
route={route}
active={activeRoute === route.key}
+ isLoading={isProjectPending}
/>
))}
@@ -305,6 +308,7 @@ const ProjectLinks = () => {
key={`product-routes-${i}`}
route={route}
active={activeRoute === route.key}
+ isLoading={isProjectPending}
/>
))}
@@ -320,12 +324,22 @@ const ProjectLinks = () => {
hasWarnings={securityLints.length > 0}
/>
)}
-
{menuItem}
+ }
+
if (disabled) {
return {menuItem}
}
diff --git a/packages/ui/src/components/shadcn/ui/sidebar.tsx b/packages/ui/src/components/shadcn/ui/sidebar.tsx
index 1b7521c8b4e..0f5842a90d8 100644
--- a/packages/ui/src/components/shadcn/ui/sidebar.tsx
+++ b/packages/ui/src/components/shadcn/ui/sidebar.tsx
@@ -521,6 +521,13 @@ const sidebarMenuButtonVariants = cva(
true: 'group-data-[collapsible=icon]:size-8! group-data-[collapsible=icon]:pl-1.5! group-data-[collapsible=icon]:pr-2!',
false: '',
},
+ isLoading: {
+ // When data necessary to check whether an item should be disabled is not yet available, override the styles to avoid
+ // showing the disabled state just for a moment
+ true: 'disabled:opacity-100 aria-disabled:opacity-100',
+ // If the item is not loading, fallback to the default styles so that disabled state is handled properly
+ false: '',
+ },
},
defaultVariants: {
variant: 'default',
@@ -537,6 +544,7 @@ const SidebarMenuButton = React.forwardRef<
isActive?: boolean
tooltip?: string | React.ComponentProps
+
+ )
+ }
+
+ return (
+
+
+ Go back to old logs
+Use the traditional interface
+
+
+ )
+}
diff --git a/apps/studio/components/layouts/LogsLayout/LogsLayout.tsx b/apps/studio/components/layouts/LogsLayout/LogsLayout.tsx
index 36176eb3da8..9d2af4613f3 100644
--- a/apps/studio/components/layouts/LogsLayout/LogsLayout.tsx
+++ b/apps/studio/components/layouts/LogsLayout/LogsLayout.tsx
@@ -25,7 +25,7 @@ const LogsLayout = ({ title, children }: PropsWithChildren+ Try Unified Logs +
+
+
+
+
-
Logs
+
+ Beta }
+
{table.getState().columnFilters.length ? Logs
+ {isUnifiedLogsEligible &&
- {isUnifiedLogsEligible && (
- {
*/
await page.goto(toUrl(`/project/${ref}/logs/${logPage.route}`))
- await expect(page.getByRole('heading', { name: 'Logs & Analytics' }), {
- message: 'Logs & Analytics heading should be visible',
+ await expect(page.getByRole('heading', { name: 'Logs', exact: true }), {
+ message: 'Logs heading should be visible',
}).toBeVisible()
/**
From c1fcec6901217d87d5972b487847ce833887bcbb Mon Sep 17 00:00:00 2001
From: Tyler
Date: Tue, 16 Jun 2026 21:21:03 +0900
Subject: [PATCH 015/488] chore: Update stats on careers page (#46978)
## I have read the
[CONTRIBUTING.md](https://github.com/supabase/supabase/blob/master/CONTRIBUTING.md)
file.
YES
## What kind of change does this PR introduce?
Update the career page stats
## Summary by CodeRabbit
* **Chores**
* Updated the career page company metrics: team members increased to
350+, countries expanded to 60+, and total capital raised updated to
$1B.
---------
Co-authored-by: Ivan Vasilov
---
apps/www/data/career.json | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/apps/www/data/career.json b/apps/www/data/career.json
index 7d1672ab0f4..42349510741 100644
--- a/apps/www/data/career.json
+++ b/apps/www/data/career.json
@@ -1,15 +1,15 @@
{
"company": [
{
- "number": "280+",
- "text": "team members\n\nin 55+ countries"
+ "number": "350+",
+ "text": "team members\n\nin 60+ countries"
},
{
"number": "20+",
"text": "languages spoken"
},
{
- "number": "$500M",
+ "number": "$1B",
"text": "raised"
},
{
@@ -17,7 +17,7 @@
"text": "community members"
},
{
- "number": "30,000+",
+ "number": "40,000+",
"text": "memes posted\n\n(and counting)"
}
],
From ccf18fe9044b6eac45740a0a6c66d562be69c768 Mon Sep 17 00:00:00 2001
From: Joshen Lim
Date: Tue, 16 Jun 2026 22:02:04 +0800
Subject: [PATCH 016/488] Prevent refetch on focus and reconnect for /query
requests that failed due to statement timeouts (#46972)
## Context
As per PR title - prevents refetch on focus and reconnect for /query
requests that failed due to statement timeouts, presumably that those
requests will run into the same problem either way so this minimizes
unnecessary impact to the database
## Summary by CodeRabbit
* **Bug Fixes**
* Improved handling of statement timeouts to prevent automatic retry
attempts after window focus or reconnection.
* Enhanced query execution request identification for better query
tracking.
---
apps/studio/data/query-client.ts | 21 +++++++++++++++++++++
1 file changed, 21 insertions(+)
diff --git a/apps/studio/data/query-client.ts b/apps/studio/data/query-client.ts
index 43306d39139..6f7b578c6a5 100644
--- a/apps/studio/data/query-client.ts
+++ b/apps/studio/data/query-client.ts
@@ -20,6 +20,16 @@ const SKIP_RETRY_PATHNAME_MATCHERS = [
export const MAX_RETRY_FAILURE_COUNT = 3
+function isQueryEndpointStatementTimeout(error: unknown) {
+ const PG_META_QUERY_PATHNAME_MATCHER = match('/platform/pg-meta/:ref/query')
+ return (
+ error instanceof ResponseError &&
+ !!error.requestPathname &&
+ !!PG_META_QUERY_PATHNAME_MATCHER(error.requestPathname) &&
+ !!error.message?.includes('canceling statement due to statement timeout')
+ )
+}
+
let queryClient: QueryClient | undefined
export function getQueryClient() {
@@ -71,6 +81,17 @@ export function getQueryClient() {
// react-query default: doubles, starting at 1000ms, with each attempt, but will not exceed 30 seconds
return Math.min(1000 * 2 ** failureCount, 30000)
},
+ refetchOnWindowFocus(query) {
+ // [Joshen] Opting to not refetch a /query request that failed due to a statement
+ // timeout, presumably that it'll just run into the same issue. Can however be overriden
+ // on a per case basis on each individual query hook
+ if (isQueryEndpointStatementTimeout(query.state.error)) return false
+ return true
+ },
+ refetchOnReconnect(query) {
+ if (isQueryEndpointStatementTimeout(query.state.error)) return false
+ return true
+ },
},
},
})
From 0c9eb15cbab161e4af4f099b73c8a5c9be549547 Mon Sep 17 00:00:00 2001
From: Jordi Enric <37541088+jordienr@users.noreply.github.com>
Date: Tue, 16 Jun 2026 16:17:28 +0200
Subject: [PATCH 017/488] refactor(studio): remove legacy homepage usage
section (V1) (#46994)
## Problem
The homepage usage section had two implementations gated by the
`newHomepageUsageV2` ConfigCat flag, with the legacy V1 as the fallback.
That flag has been at 100% in production for months, so V1 is dead code
and the flag branch is unnecessary.
## Fix
- Make V2 the default by removing the `newHomepageUsageV2` flag check in
`Home.tsx`.
- Delete the V1 section (`Home/ProjectUsageSection.tsx`), its chart
(`Home/ProjectUsage.tsx`), and the now-orphaned
`project-log-requests-count-query` plus its query key.
- Shared code (`useProjectLogStatsQuery`, `UsageApiCounts`,
`ProjectLogStatsVariables`) is kept since V2 and other modules still use
it.
The `newHomepageUsageV2` flag can be removed from ConfigCat after this
merges.
## How to test
- Open a project homepage on platform.
- Confirm the usage section still renders (the V2 layout) with no flag
dependency.
- Verify no console errors and no broken imports.
- Expected result: identical homepage usage section to what production
shows today.
## Notes
- This is independent of the in-flight service-health usage charts work
(PR #46373), which is behind its own `newHomepageUsageDeltas` flag.
Whichever merges second will resolve a small conflict on the
`UsageSection` selection in `Home.tsx`.
## Summary by CodeRabbit
* **Refactor**
* Removed project usage statistics section from the home page.
* Simplified the home page experience by consolidating feature flag
variants into a standardized implementation.
Co-authored-by: Claude Opus 4.8
---
.../interfaces/Home/ProjectUsage.tsx | 238 ------------------
.../interfaces/Home/ProjectUsageSection.tsx | 38 ---
.../interfaces/ProjectHome/Home.tsx | 11 +-
apps/studio/data/analytics/keys.ts | 3 -
.../project-log-requests-count-query.ts | 58 -----
5 files changed, 3 insertions(+), 345 deletions(-)
delete mode 100644 apps/studio/components/interfaces/Home/ProjectUsage.tsx
delete mode 100644 apps/studio/components/interfaces/Home/ProjectUsageSection.tsx
delete mode 100644 apps/studio/data/analytics/project-log-requests-count-query.ts
diff --git a/apps/studio/components/interfaces/Home/ProjectUsage.tsx b/apps/studio/components/interfaces/Home/ProjectUsage.tsx
deleted file mode 100644
index abf36066ec2..00000000000
--- a/apps/studio/components/interfaces/Home/ProjectUsage.tsx
+++ /dev/null
@@ -1,238 +0,0 @@
-import { useParams } from 'common'
-import dayjs from 'dayjs'
-import { Auth, Database, Realtime, Storage } from 'icons'
-import sumBy from 'lodash/sumBy'
-import Link from 'next/link'
-import { useRouter } from 'next/router'
-import { useEffect, useState } from 'react'
-import { Loading } from 'ui'
-
-import BarChart from '@/components/ui/Charts/BarChart'
-import { ChartIntervalDropdown } from '@/components/ui/Logs/ChartIntervalDropdown'
-import { CHART_INTERVALS } from '@/components/ui/Logs/logs.utils'
-import Panel from '@/components/ui/Panel'
-import {
- ProjectLogStatsVariables,
- UsageApiCounts,
- useProjectLogStatsQuery,
-} from '@/data/analytics/project-log-stats-query'
-import { useFillTimeseriesSorted } from '@/hooks/analytics/useFillTimeseriesSorted'
-import { useCheckEntitlements } from '@/hooks/misc/useCheckEntitlements'
-import { useIsFeatureEnabled } from '@/hooks/misc/useIsFeatureEnabled'
-import { useSelectedOrganizationQuery } from '@/hooks/misc/useSelectedOrganization'
-
-type ChartIntervalKey = ProjectLogStatsVariables['interval']
-
-const ProjectUsage = () => {
- const router = useRouter()
- const { ref: projectRef } = useParams()
- const { data: organization } = useSelectedOrganizationQuery()
-
- const { projectAuthAll: authEnabled, projectStorageAll: storageEnabled } = useIsFeatureEnabled([
- 'project_auth:all',
- 'project_storage:all',
- ])
-
- const { getEntitlementMax } = useCheckEntitlements('log.retention_days')
- const retentionDays = getEntitlementMax()
-
- const DEFAULT_INTERVAL: ChartIntervalKey =
- retentionDays !== undefined && retentionDays < 7 ? '1hr' : '1day'
-
- const [interval, setInterval] = useState(DEFAULT_INTERVAL)
-
- useEffect(() => {
- setInterval(retentionDays !== undefined && retentionDays < 7 ? '1hr' : '1day')
- }, [retentionDays])
-
- const { data, isPending: isLoading } = useProjectLogStatsQuery({ projectRef, interval })
-
- const selectedInterval = CHART_INTERVALS.find((i) => i.key === interval) || CHART_INTERVALS[1]
- const startDateLocal = dayjs().subtract(
- selectedInterval.startValue,
- selectedInterval.startUnit as dayjs.ManipulateType
- )
- const endDateLocal = dayjs()
- const { data: charts } = useFillTimeseriesSorted({
- data: data?.result ?? [],
- timestampKey: 'timestamp',
- valueKey: [
- 'total_auth_requests',
- 'total_rest_requests',
- 'total_storage_requests',
- 'total_realtime_requests',
- ],
- defaultValue: 0,
- startDate: startDateLocal.toISOString(),
- endDate: endDateLocal.toISOString(),
- minPointsToFill: 5,
- })
- const datetimeFormat = selectedInterval.format || 'MMM D, ha'
-
- const handleBarClick = (
- value: UsageApiCounts,
- _type: 'rest' | 'realtime' | 'storage' | 'auth'
- ) => {
- const unit = selectedInterval.startUnit
- const selectedStart = dayjs(value?.timestamp)
- const selectedEnd = selectedStart.add(1, unit)
-
- if (_type === 'rest') {
- router.push(
- `/project/${projectRef}/logs/edge-logs?its=${selectedStart.toISOString()}&ite=${selectedEnd.toISOString()}`
- )
- return
- }
-
- router.push(
- `/project/${projectRef}/logs/edge-logs?its=${selectedStart.toISOString()}&ite=${selectedEnd.toISOString()}&f=${JSON.stringify(
- {
- product: {
- [_type]: true,
- },
- }
- )}`
- )
- }
-
- return (
-
- handleBarClick(v as UsageApiCounts, 'auth')}
- customDateFormat={datetimeFormat}
- highlightedValue={sumBy(charts || [], 'total_auth_requests')}
- />
-
-
-
- )}
- {storageEnabled && (
-
-
-
-
- }
- title="Storage"
- href={`/project/${projectRef}/storage/buckets`}
- />
-
-
-
- handleBarClick(v as UsageApiCounts, 'rest')}
- customDateFormat={datetimeFormat}
- highlightedValue={sumBy(charts, 'total_rest_requests')}
- />
-
-
-
- {authEnabled && (
-
-
-
-
- }
- title="Auth"
- href={`/project/${projectRef}/auth/users`}
- />
-
- setInterval(interval as ProjectLogStatsVariables['interval'])}
- organizationSlug={organization?.slug}
- dropdownAlign="start"
- tooltipSide="right"
- />
-
- Statistics for {selectedInterval.label.toLowerCase()}
-
-
-
-
-
-
-
- }
- title="Database"
- href={`/project/${projectRef}/editor`}
- />
-
-
-
- {props.icon}
-
- {props.title}
- -
-
- Publications with no tables are hidden -
-- No publications available -
+
+
)}
- No publications available
+Publications with no tables are hidden
+
{failure.name}
- {failure.failure_type === 'critical' &&
-
+ This destination type is in alpha and may change while we iterate.{' '}
+
+ Leave feedback
+
+
+ )
+ }
+ >
-
- {selectedOption?.isAlpha && (
-
+
)
}
diff --git a/apps/studio/data/replication/validate-destination-mutation.ts b/apps/studio/data/replication/validate-destination-mutation.ts
index 1bd7aeaecd0..848879e6e50 100644
--- a/apps/studio/data/replication/validate-destination-mutation.ts
+++ b/apps/studio/data/replication/validate-destination-mutation.ts
@@ -8,13 +8,28 @@ import type { ResponseError, UseCustomMutationOptions } from '@/types'
type ValidateDestinationParams = {
projectRef: string
destinationConfig: DestinationConfig
+ sourceId?: number
+ publicationName?: string
+ maxFillMs?: number
+ maxTableSyncWorkers?: number
+ maxCopyConnectionsPerTable?: number
+ invalidatedSlotBehavior?: 'error' | 'recreate'
}
type ValidateDestinationResponse = components['schemas']['ValidateDestinationResponse']
export type ValidationFailure = ValidateDestinationResponse['validation_failures'][number]
async function validateDestination(
- { projectRef, destinationConfig }: ValidateDestinationParams,
+ {
+ projectRef,
+ destinationConfig,
+ sourceId,
+ publicationName,
+ maxFillMs,
+ maxTableSyncWorkers,
+ maxCopyConnectionsPerTable,
+ invalidatedSlotBehavior,
+ }: ValidateDestinationParams,
signal?: AbortSignal
): Promise
-
-
+ Type
-- The destination type cannot be changed after creation. -
-
- This destination type is in alpha and may change while we iterate.{' '}
-
diff --git a/apps/studio/components/interfaces/Support/SupportFormV2.tsx b/apps/studio/components/interfaces/Support/SupportFormV2.tsx
index 5b60aa92a1d..17d6ad0e884 100644
--- a/apps/studio/components/interfaces/Support/SupportFormV2.tsx
+++ b/apps/studio/components/interfaces/Support/SupportFormV2.tsx
@@ -114,6 +114,7 @@ export const SupportFormV2 = ({ form, initialError, state, dispatch }: SupportFo
dispatch({
type: 'ERROR',
message: error.message,
+ code: error.code,
})
},
})
diff --git a/apps/studio/components/interfaces/Support/SupportFormV3.tsx b/apps/studio/components/interfaces/Support/SupportFormV3.tsx
index c86f463cc09..553dd433d88 100644
--- a/apps/studio/components/interfaces/Support/SupportFormV3.tsx
+++ b/apps/studio/components/interfaces/Support/SupportFormV3.tsx
@@ -122,6 +122,7 @@ export const SupportFormV3 = ({
dispatch({
type: 'ERROR',
message: error.message,
+ code: error.code,
})
},
})
diff --git a/apps/studio/components/interfaces/Support/SupportSidebarForm.tsx b/apps/studio/components/interfaces/Support/SupportSidebarForm.tsx
index 40b0288d6ea..fa910e1db52 100644
--- a/apps/studio/components/interfaces/Support/SupportSidebarForm.tsx
+++ b/apps/studio/components/interfaces/Support/SupportSidebarForm.tsx
@@ -70,7 +70,9 @@ export function SupportForm({ initialParams }: SupportFormProps) {
useStateTransition(state, 'submitting', 'error', (_, curr) => {
toast.error(`Failed to submit support ticket: ${curr.message}`)
- Sentry.captureMessage(`Failed to submit Support Form: ${curr.message}`)
+ if (curr.code !== 429) {
+ Sentry.captureMessage(`Failed to submit Support Form: ${curr.message}`)
+ }
dispatch({ type: 'RETURN_TO_EDITING' })
})
diff --git a/apps/studio/data/feedback/support-ticket-send.ts b/apps/studio/data/feedback/support-ticket-send.ts
index 8e14bf50b40..37957dce243 100644
--- a/apps/studio/data/feedback/support-ticket-send.ts
+++ b/apps/studio/data/feedback/support-ticket-send.ts
@@ -5,7 +5,8 @@ import { toast } from 'sonner'
import type { ExtendedSupportCategories } from '@/components/interfaces/Support/Support.constants'
import { handleError, post } from '@/data/fetchers'
-import type { ResponseError, UseCustomMutationOptions } from '@/types'
+import { ResponseError } from '@/types'
+import type { UseCustomMutationOptions } from '@/types'
export type sendSupportTicketVariables = {
subject: string
@@ -25,6 +26,8 @@ export type sendSupportTicketVariables = {
dashboardStudioVersion?: string
}
+const RATE_LIMIT_FALLBACK_SECONDS = 60
+
export async function sendSupportTicket({
subject,
message,
@@ -42,7 +45,7 @@ export async function sendSupportTicket({
dashboardLogs,
dashboardStudioVersion,
}: sendSupportTicketVariables) {
- const { data, error } = await post('/platform/feedback/send', {
+ const { data, error, response } = await post('/platform/feedback/send', {
body: {
subject,
message,
@@ -65,6 +68,20 @@ export async function sendSupportTicket({
})
if (error) {
+ const httpResponse: unknown = response
+ if (httpResponse instanceof Response && httpResponse.status === 429) {
+ const resetHeader =
+ httpResponse.headers.get('Retry-After') ?? httpResponse.headers.get('X-RateLimit-Reset')
+ const parsedReset = resetHeader ? parseInt(resetHeader, 10) : NaN
+ const waitSeconds = Number.isFinite(parsedReset) ? parsedReset : RATE_LIMIT_FALLBACK_SECONDS
+ throw new ResponseError(
+ `You have submitted too many support requests. Please try again in ${waitSeconds} second${waitSeconds === 1 ? '' : 's'}.`,
+ 429,
+ undefined,
+ waitSeconds
+ )
+ }
+
handleError(error, {
alwaysCapture: true,
sentryContext: {
diff --git a/apps/studio/data/fetchers.ts b/apps/studio/data/fetchers.ts
index 7e71e9dd686..1ce51f26e80 100644
--- a/apps/studio/data/fetchers.ts
+++ b/apps/studio/data/fetchers.ts
@@ -140,7 +140,8 @@ client.use(
body.requestId = request.headers.get('X-Request-Id')
- const retryAfterHeader = response.headers.get('Retry-After')
+ const retryAfterHeader =
+ response.headers.get('Retry-After') ?? response.headers.get('X-RateLimit-Reset')
body.retryAfter = retryAfterHeader ? parseInt(retryAfterHeader) : undefined
const requestUrl = new URL(request.url)
@@ -296,10 +297,11 @@ async function handleFetchError(response: unknown): Promise {
resJson.msg ??
resJson.error ??
`An error has occurred: ${status ?? 'Unknown error'}`
- const retryAfter =
- response instanceof Response && response.headers.get('Retry-After')
- ? parseInt(response.headers.get('Retry-After')!)
- : undefined
+ const retryAfterHeader =
+ response instanceof Response
+ ? (response.headers.get('Retry-After') ?? response.headers.get('X-RateLimit-Reset'))
+ : null
+ const retryAfter = retryAfterHeader ? parseInt(retryAfterHeader) : undefined
let error = new ResponseError(message, status, undefined, retryAfter)
From f70e9c49ff6af86c9d77295c6803f50e14a7fcfb Mon Sep 17 00:00:00 2001
From: mo khan
Date: Tue, 16 Jun 2026 09:03:15 -0600
Subject: [PATCH 021/488] docs: Add @xlgmokha to humans.txt (#46995)
## I have read the
[CONTRIBUTING.md](https://github.com/supabase/supabase/blob/master/CONTRIBUTING.md)
file.
YES
## What kind of change does this PR introduce?
docs update
## What is the current behavior?
N/A
## What is the new behavior?
N/A
## Additional context
Following the instructions from the onboarding guide.
## Summary by CodeRabbit
* **Chores**
* Updated team information.
---
apps/docs/public/humans.txt | 1 +
1 file changed, 1 insertion(+)
diff --git a/apps/docs/public/humans.txt b/apps/docs/public/humans.txt
index a2765dcef91..f419811b211 100644
--- a/apps/docs/public/humans.txt
+++ b/apps/docs/public/humans.txt
@@ -199,6 +199,7 @@ Mert Yerekapan
Michal Kleczek
Michelle Jubrey
Miranda Limonczenko
+Mo Khan
Monica Khoury
Mrinal Paliwal
Mykhailo Mischa Lieibenson
From 79ce3b4ec7c8426cae82c8b5eb7ff98c3eddf1da Mon Sep 17 00:00:00 2001
From: "kemal.earth" <606977+kemaldotearth@users.noreply.github.com>
Date: Tue, 16 Jun 2026 16:39:39 +0100
Subject: [PATCH 022/488] fix(studio): hide throughput row on review modal for
io2 (#46997)
## I have read the
[CONTRIBUTING.md](https://github.com/supabase/supabase/blob/master/CONTRIBUTING.md)
file.
YES
## What kind of change does this PR introduce?
When a user selects IO2 on compute upgrade, the `0/MB` isn't quite
correct, whilst the costa delta of $0 is correct. We will hide the row
as it adds noise.
## Summary by CodeRabbit
* **Bug Fixes**
* Fixed disk management UI to correctly display the throughput
configuration row only when selecting GP3 storage type, ensuring the
interface accurately reflects available options for the selected storage
type.
---
.../DiskManagementReviewAndSubmitDialog.hooks.ts | 9 +++++----
1 file changed, 5 insertions(+), 4 deletions(-)
diff --git a/apps/studio/components/interfaces/DiskManagement/DiskManagementReviewAndSubmitDialog/DiskManagementReviewAndSubmitDialog.hooks.ts b/apps/studio/components/interfaces/DiskManagement/DiskManagementReviewAndSubmitDialog/DiskManagementReviewAndSubmitDialog.hooks.ts
index 9505d1d6cbb..954a1ac0a5d 100644
--- a/apps/studio/components/interfaces/DiskManagement/DiskManagementReviewAndSubmitDialog/DiskManagementReviewAndSubmitDialog.hooks.ts
+++ b/apps/studio/components/interfaces/DiskManagement/DiskManagementReviewAndSubmitDialog/DiskManagementReviewAndSubmitDialog.hooks.ts
@@ -120,7 +120,6 @@ export function useDiskManagementReviewChanges(
// --- Derived predicates ---
- const storageTypeBefore = (form.formState.defaultValues?.storageType ?? '') as DiskType
const storageTypeAfter = form.getValues('storageType') as DiskType
// Show hero whenever any line-item price actually changes, not just compute
@@ -132,12 +131,14 @@ export function useDiskManagementReviewChanges(
// Show cooldown warning whenever any disk attribute that enforces the 4-hour lock changes
const anyDiskAttributeChange = hasIOPSChanges || hasStorageTypeChanges || hasTotalSizeChanges
- // Show throughput row whenever either the before or after storage type is GP3
- // (covers GP3→IO2 where the throughput charge drops to zero)
+ // Throughput is only a user-configurable, separately-billed attribute for GP3. For IO2 it is
+ // derived from provisioned IOPS (0.256 MiB/s per IOPS) and isn't surfaced as its own value, so
+ // the form clears it to 0 — rendering a misleading "→ 0 MB/s". Only show the row when the
+ // resulting storage type is GP3; any GP3→IO2 throughput price delta still lands in the total.
const showThroughputRow =
!isAwsK8sProject &&
!isAwsNimbus &&
- (storageTypeBefore === 'gp3' || storageTypeAfter === 'gp3') &&
+ storageTypeAfter === 'gp3' &&
(hasThroughputChanges || hasStorageTypeChanges)
const hasAnyBreakdownRows =
From 92e79e67d9f573157fd7f60869214db113e7d478 Mon Sep 17 00:00:00 2001
From: Ivan Vasilov
Date: Tue, 16 Jun 2026 19:18:17 +0300
Subject: [PATCH 023/488] feat: Add error state to charts (#46991)
This PR adds an error state to the usage charts on the Project home
page.
I also added an error state to the charts in the [design
system](https://design-system-git-feat-chart-error-state-supabase.vercel.app/design-system/docs/ui-patterns/charts#chart-states).
## Summary by CodeRabbit
* **New Features**
* Charts now display error states when data retrieval or processing
fails, providing users with clear feedback about issues.
* Improved error visibility and handling across analytics and charting
components for better transparency.
---
.../default/block/chart-composed-states.tsx | 31 ++++++-
.../ProjectHome/ProjectUsageSection.tsx | 78 +++++++++-------
.../analytics/useFillTimeseriesSorted.ts | 88 ++++++++++---------
packages/ui-patterns/src/Chart/index.tsx | 16 +++-
.../ui-patterns/src/LogsBarChart/index.tsx | 9 ++
5 files changed, 147 insertions(+), 75 deletions(-)
diff --git a/apps/design-system/registry/default/block/chart-composed-states.tsx b/apps/design-system/registry/default/block/chart-composed-states.tsx
index c4e25d545c2..2d3657cca2c 100644
--- a/apps/design-system/registry/default/block/chart-composed-states.tsx
+++ b/apps/design-system/registry/default/block/chart-composed-states.tsx
@@ -1,7 +1,7 @@
'use client'
import { BarChart2, ExternalLink } from 'lucide-react'
-import { Badge } from 'ui'
+import { Badge, CriticalIcon } from 'ui'
import {
Chart,
ChartActions,
@@ -44,6 +44,35 @@ export default function ChartComposedStates() {
+
+
+
+ Response Errors
+
+
+
+
diff --git a/apps/studio/components/interfaces/ProjectHome/ProjectUsageSection.tsx b/apps/studio/components/interfaces/ProjectHome/ProjectUsageSection.tsx
index 54c02299725..db61af89df2 100644
--- a/apps/studio/components/interfaces/ProjectHome/ProjectUsageSection.tsx
+++ b/apps/studio/components/interfaces/ProjectHome/ProjectUsageSection.tsx
@@ -3,15 +3,16 @@ import dayjs from 'dayjs'
import Link from 'next/link'
import { useRouter } from 'next/router'
import { useEffect, useMemo, useState } from 'react'
-import { Card, CardContent, CardHeader, CardTitle, Loading } from 'ui'
+import { Card, CardContent, CardHeader, CardTitle, Loading, WarningIcon } from 'ui'
import { Row } from 'ui-patterns'
+import { ChartEmptyState } from 'ui-patterns/Chart'
import { LogsBarChart } from 'ui-patterns/LogsBarChart'
import NoDataPlaceholder from '@/components/ui/Charts/NoDataPlaceholder'
import { ChartIntervalDropdown } from '@/components/ui/Logs/ChartIntervalDropdown'
import { CHART_INTERVALS } from '@/components/ui/Logs/logs.utils'
import { UsageApiCounts, useProjectLogStatsQuery } from '@/data/analytics/project-log-stats-query'
-import { useFillTimeseriesSorted } from '@/hooks/analytics/useFillTimeseriesSorted'
+import { fillTimeseriesSorted } from '@/hooks/analytics/useFillTimeseriesSorted'
import { useCheckEntitlements } from '@/hooks/misc/useCheckEntitlements'
import { useIsFeatureEnabled } from '@/hooks/misc/useIsFeatureEnabled'
import { useSelectedOrganizationQuery } from '@/hooks/misc/useSelectedOrganization'
@@ -71,33 +72,42 @@ export const ProjectUsageSection = () => {
}, [selectedInterval])
// Use V1 data fetching
- const { data: logStatsData, isPending: isLoading } = useProjectLogStatsQuery({
- projectRef,
- interval,
- })
+ const {
+ data: filledCharts,
+ isPending: isLoading,
+ error,
+ } = useProjectLogStatsQuery(
+ {
+ projectRef,
+ interval,
+ },
+ {
+ select: (data) => {
+ // Calculate date range for gap filling
+ const startDateLocal = dayjs().subtract(
+ selectedInterval.startValue,
+ selectedInterval.startUnit as dayjs.ManipulateType
+ )
+ const endDateLocal = dayjs()
- // Calculate date range for gap filling
- const startDateLocal = dayjs().subtract(
- selectedInterval.startValue,
- selectedInterval.startUnit as dayjs.ManipulateType
+ return fillTimeseriesSorted({
+ data: data.result,
+ timestampKey: 'timestamp',
+ valueKey: [
+ 'total_auth_requests',
+ 'total_rest_requests',
+ 'total_storage_requests',
+ 'total_realtime_requests',
+ ],
+ defaultValue: 0,
+ startDate: startDateLocal.toISOString(),
+ endDate: endDateLocal.toISOString(),
+ minPointsToFill: 5,
+ })
+ },
+ refetchOnWindowFocus: false,
+ }
)
- const endDateLocal = dayjs()
-
- // Fill gaps in timeseries data
- const { data: filledCharts } = useFillTimeseriesSorted({
- data: logStatsData?.result ?? [],
- timestampKey: 'timestamp',
- valueKey: [
- 'total_auth_requests',
- 'total_rest_requests',
- 'total_storage_requests',
- 'total_realtime_requests',
- ],
- defaultValue: 0,
- startDate: startDateLocal.toISOString(),
- endDate: endDateLocal.toISOString(),
- minPointsToFill: 5,
- })
const serviceBase: ServiceEntry[] = useMemo(
() => [
@@ -147,7 +157,7 @@ export const ProjectUsageSection = () => {
// Transform V1 data to LogsBarChart format
// Since V1 doesn't have error/warning breakdown, we show everything as "ok"
- const transformedData: LogsBarChartDatum[] = (filledCharts || []).map((item) => ({
+ const transformedData: LogsBarChartDatum[] = (filledCharts?.data || []).map((item) => ({
timestamp: item.timestamp,
error_count: 0,
warning_count: 0,
@@ -162,10 +172,10 @@ export const ProjectUsageSection = () => {
data: transformedData,
total,
isLoading,
- error: null,
+ error: error || filledCharts?.error || null,
}
}),
- [serviceBase, filledCharts, isLoading]
+ [serviceBase, filledCharts, isLoading, error]
)
const handleBarClick =
@@ -239,6 +249,7 @@ export const ProjectUsageSection = () => {
{
label: 'Requests',
},
}}
+ ErrorState={
+ (data: T[], timestampKey: stri
*/
export const useFillTimeseriesSorted = (
options: FillTimeseriesOptions
+): FillTimeseriesResult => {
+ return useMemo(() => {
+ return fillTimeseriesSorted(options)
+ }, [
+ JSON.stringify(options.data),
+ options.timestampKey,
+ JSON.stringify(options.valueKey),
+ options.defaultValue,
+ options.startDate,
+ options.endDate,
+ options.minPointsToFill,
+ options.interval,
+ ])
+}
+
+export const fillTimeseriesSorted = (
+ options: FillTimeseriesOptions
): FillTimeseriesResult => {
const {
data,
@@ -78,50 +95,39 @@ export const useFillTimeseriesSorted = (
interval,
} = options
- return useMemo(() => {
- // Early return if no valid timestamp
- if (!hasValidTimestamp(data, timestampKey)) {
- return {
- data,
- error: null,
- isError: false,
- }
+ // Early return if no valid timestamp
+ if (!hasValidTimestamp(data, timestampKey)) {
+ return {
+ data,
+ error: null,
+ isError: false,
}
+ }
- try {
- const filled = fillTimeseries(
- data,
- timestampKey,
- valueKey,
- defaultValue,
- startDate,
- endDate,
- minPointsToFill,
- interval
- ) as T[]
+ try {
+ const filled = fillTimeseries(
+ data,
+ timestampKey,
+ valueKey,
+ defaultValue,
+ startDate,
+ endDate,
+ minPointsToFill,
+ interval
+ ) as T[]
- const sorted = sortByTimestamp(filled, timestampKey)
+ const sorted = sortByTimestamp(filled, timestampKey)
- return {
- data: sorted,
- error: null,
- isError: false,
- }
- } catch (error: unknown) {
- return {
- data: [],
- error: error instanceof Error ? error : new Error(String(error)),
- isError: true,
- }
+ return {
+ data: sorted,
+ error: null,
+ isError: false,
}
- }, [
- JSON.stringify(data),
- timestampKey,
- JSON.stringify(valueKey),
- defaultValue,
- startDate,
- endDate,
- minPointsToFill,
- interval,
- ])
+ } catch (error: unknown) {
+ return {
+ data: [],
+ error: error instanceof Error ? error : new Error(String(error)),
+ isError: true,
+ }
+ }
}
diff --git a/packages/ui-patterns/src/Chart/index.tsx b/packages/ui-patterns/src/Chart/index.tsx
index ca9773a529a..3c0937a6159 100644
--- a/packages/ui-patterns/src/Chart/index.tsx
+++ b/packages/ui-patterns/src/Chart/index.tsx
@@ -43,11 +43,13 @@ export type ChartConfig = {
interface ChartContextValue {
isLoading?: boolean
isDisabled?: boolean
+ isErrored?: boolean
}
const ChartContext = React.createContext({
isLoading: false,
isDisabled: false,
+ isErrored: false,
})
export const useChart = () => {
@@ -59,15 +61,19 @@ interface ChartProps extends React.HTMLAttributes {
children: React.ReactNode
isLoading?: boolean
isDisabled?: boolean
+ isErrored?: boolean
className?: string
}
const chartTableClasses = `[&_tr]:border-b [&_tr]:border-border [&_thead_tr]:bg-transparent! [&_thead_th]:py-2! [&_thead_th]:!px-card [&_thead_th]:h-auto [&_tbody_td]:py-2.5 [&_tbody_td]:px-card [&_tbody_td]:text-xs [&_table]:mb-1 [&_table]:border-b [&_table]:border-border`
const Chart = React.forwardRef(
- ({ children, isLoading = false, isDisabled = false, className, ...props }, ref) => {
+ (
+ { children, isLoading = false, isDisabled = false, isErrored = false, className, ...props },
+ ref
+ ) => {
return (
-
+
{
isEmpty?: boolean
emptyState?: React.ReactNode
loadingState?: React.ReactNode
+ errorState?: React.ReactNode
disabledState?: React.ReactNode
disabledActions?: ChartAction[]
}
@@ -318,19 +325,22 @@ const ChartContent = React.forwardRef(
isEmpty = false,
emptyState,
loadingState,
+ errorState,
disabledState,
disabledActions,
...props
},
ref
) => {
- const { isLoading, isDisabled } = useChart()
+ const { isLoading, isDisabled, isErrored } = useChart()
let content: React.ReactNode
if (isDisabled) {
content = disabledState
} else if (isLoading) {
content = loadingState
+ } else if (isErrored) {
+ content = errorState
} else if (isEmpty) {
content = emptyState
} else {
diff --git a/packages/ui-patterns/src/LogsBarChart/index.tsx b/packages/ui-patterns/src/LogsBarChart/index.tsx
index 20316fc438f..c0ad0476d8b 100644
--- a/packages/ui-patterns/src/LogsBarChart/index.tsx
+++ b/packages/ui-patterns/src/LogsBarChart/index.tsx
@@ -26,8 +26,10 @@ type LogsBarChartDatum = {
export const LogsBarChart = ({
data,
+ error,
onBarClick,
EmptyState,
+ ErrorState,
DateTimeFormat = 'MMM D, YYYY, hh:mma',
isFullHeight = false,
chartConfig,
@@ -36,8 +38,10 @@ export const LogsBarChart = ({
hideXAxis = false,
}: {
data: LogsBarChartDatum[]
+ error?: unknown | null
onBarClick?: (datum: LogsBarChartDatum, tooltipData?: CategoricalChartState) => void
EmptyState?: ReactNode
+ ErrorState?: ReactNode
DateTimeFormat?: string
isFullHeight?: boolean
chartConfig?: ChartConfig
@@ -47,6 +51,11 @@ export const LogsBarChart = ({
}) => {
const [focusDataIndex, setFocusDataIndex] = useState(null)
+ if (error) {
+ if (ErrorState) return ErrorState
+ return null
+ }
+
if (data.length === 0) {
if (EmptyState) return EmptyState
return null
From 6a6b7c90858b6b868c6d05bd3263a957357fa84a Mon Sep 17 00:00:00 2001
From: Danny White <3104761+dnywh@users.noreply.github.com>
Date: Tue, 16 Jun 2026 12:59:37 -0600
Subject: [PATCH 024/488] fix(docs): remove redundant icons (#47002)
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
## What kind of change does this PR introduce?
UI fix. Resolves DOCS-1051.
## What is the current behavior?
Two unnecessary icons on docs homepage add more confusion than help.
## What is the new behavior?
Removed and tightened surrounding spacing + rhythm.
| Before | After |
| --- | --- |
| 
| 
|
| 
| 
|
## Summary by CodeRabbit
* **Style**
* Simplified documentation page header and section visuals by removing
icon-accented wrappers and using cleaner text-based layouts.
* **Accessibility / Content**
* Updated section heading hierarchy for improved structure (e.g.,
“Additional resources” and “Self-Hosting”) by promoting headings while
keeping existing context and styling.
* Refreshed the “Getting Started” section to be text-focused without the
prior play icon treatment.
---
apps/docs/app/page.tsx | 20 ++++++++------------
apps/docs/components/HomePageCover.tsx | 17 +++++++----------
2 files changed, 15 insertions(+), 22 deletions(-)
diff --git a/apps/docs/app/page.tsx b/apps/docs/app/page.tsx
index 186f3548a79..31eba97aef4 100644
--- a/apps/docs/app/page.tsx
+++ b/apps/docs/app/page.tsx
@@ -1,11 +1,10 @@
import { isFeatureEnabled } from 'common'
import { type Metadata, type ResolvingMetadata } from 'next'
import Link from 'next/link'
-import { cn, IconBackground } from 'ui'
+import { cn } from 'ui'
import { IconPanel } from 'ui-patterns/IconPanel'
import { TextLink } from 'ui-patterns/TextLink'
-import MenuIconPicker from '@/components/Navigation/NavigationMenu/MenuIconPicker'
import { MIGRATION_PAGES } from '@/components/Navigation/NavigationMenu/NavigationMenu.constants'
import { GlassPanelWithIconPicker } from '@/features/ui/GlassPanelWithIconPicker'
import { IconPanelWithIconPicker } from '@/features/ui/IconPanelWithIconPicker'
@@ -324,10 +323,10 @@ const HomePage = () => (
)}
{children}
@@ -306,6 +312,7 @@ interface ChartContentProps extends React.HTMLAttributes
-
-
+
{isFeatureEnabled('docs:full_getting_started') && (
+
+
Additional resources
-
+
@@ -351,17 +350,14 @@ const HomePage = () => (
Additional resources - +
-
+
{
>
-
-
-
+
+
-
+
Self-Hosting
-
+
+
Get started with self-hosting Supabase.
-
{
if (!supabaseUrl) throw new Error('supabaseUrl is required.')
if (!supabaseKey) throw new Error('supabaseKey is required.')
- // Test a simple query to the database
+ // Test a query to the database
const { data: table_data, error: table_error } = await client
.from('my_table')
.select('*')
diff --git a/apps/docs/content/guides/functions/wasm.mdx b/apps/docs/content/guides/functions/wasm.mdx
index c8377bc6e10..fe7e5f61ece 100644
--- a/apps/docs/content/guides/functions/wasm.mdx
+++ b/apps/docs/content/guides/functions/wasm.mdx
@@ -20,7 +20,7 @@ For example, libraries like [magick-wasm](/docs/guides/functions/examples/image-
### Writing a Wasm module
-You can use different languages and SDKs to write Wasm modules. For this tutorial, we will write a simple Wasm module in Rust that adds two numbers.
+You can use different languages and SDKs to write Wasm modules. For this tutorial, we will write a basic Wasm module in Rust that adds two numbers.
diff --git a/apps/docs/content/guides/getting-started/api-keys.mdx b/apps/docs/content/guides/getting-started/api-keys.mdx
index 696c9578bbe..3ca3976f52a 100644
--- a/apps/docs/content/guides/getting-started/api-keys.mdx
+++ b/apps/docs/content/guides/getting-started/api-keys.mdx
@@ -89,7 +89,7 @@ Never expose your secret keys publicly. Your data is at risk. **Do not:**
- Never use in a browser, even on `localhost`.
- Do not pass in URLs or query params, as these are often logged.
- Be careful passing them in request headers without prior log sanitization.
-- Take extra care logging even potentially **invalid API keys**. Simple typos might reveal the real key in the future.
+- Take extra care logging even potentially **invalid API keys**. Typos might reveal the real key in the future.
- Reveal, copy, use or manipulate on hardware devices without full disk encryption and which you do not directly own or control (such as public computers, friend's laptop, etc.)
Ensure you handle them with care and using [secure coding practices](https://owasp.org/www-project-secure-coding-practices-quick-reference-guide/stable-en/).
diff --git a/apps/docs/content/guides/getting-started/architecture.mdx b/apps/docs/content/guides/getting-started/architecture.mdx
index e75cd4ab38b..0e8767f5c3a 100644
--- a/apps/docs/content/guides/getting-started/architecture.mdx
+++ b/apps/docs/content/guides/getting-started/architecture.mdx
@@ -4,7 +4,7 @@ description: 'Supabase design and architecture'
tocVideo: 'T-qAtAKjqwc'
---
-Supabase is open source. We choose open source tools which are scalable and make them simple to use.
+Supabase is open source. We choose open source tools which are scalable and make them approachable.
Supabase is not a 1-to-1 mapping of Firebase. While we are building many of the features that Firebase offers, we are not going about it the same way:
our technological choices are quite different; everything we use is open source; and wherever possible, we use and support existing tools rather than developing from scratch.
@@ -13,7 +13,7 @@ Most notably, we use Postgres rather than a NoSQL store. This choice was deliber
## Choose your comfort level
-Our goal at Supabase is to make _all_ of Postgres easy to use. That doesn’t mean you have to use all of it. If you’re a Postgres veteran, you’ll probably love the tools that we offer. If you’ve never used Postgres before, then start smaller and grow into it. If you just want to treat Postgres like a simple table-store, that’s perfectly fine.
+Our goal at Supabase is to make _all_ of Postgres easy to use. That doesn’t mean you have to use all of it. If you’re a Postgres veteran, you’ll probably love the tools that we offer. If you’ve never used Postgres before, then start smaller and grow into it. If you want to treat Postgres like a basic table-store, that’s perfectly fine.
## Architecture
diff --git a/apps/docs/content/guides/getting-started/features.mdx b/apps/docs/content/guides/getting-started/features.mdx
index 8dcb43769e0..d27f2ca8a6d 100644
--- a/apps/docs/content/guides/getting-started/features.mdx
+++ b/apps/docs/content/guides/getting-started/features.mdx
@@ -128,7 +128,7 @@ Helpers for implementing user authentication in popular server-side languages an
### File storage
-Supabase Storage makes it simple to store and serve files. [Docs](/docs/guides/storage).
+Supabase Storage helps you store and serve files. [Docs](/docs/guides/storage).
### Content Delivery Network
diff --git a/apps/docs/content/guides/getting-started/quickstarts/laravel.mdx b/apps/docs/content/guides/getting-started/quickstarts/laravel.mdx
index 381caecf2e5..6e7744279bf 100644
--- a/apps/docs/content/guides/getting-started/quickstarts/laravel.mdx
+++ b/apps/docs/content/guides/getting-started/quickstarts/laravel.mdx
@@ -29,7 +29,7 @@ hideToc: true
- Install [Laravel Breeze](https://laravel.com/docs/10.x/starter-kits#laravel-breeze), a simple implementation of all of Laravel's [authentication features](https://laravel.com/docs/10.x/authentication).
+ Install [Laravel Breeze](https://laravel.com/docs/10.x/starter-kits#laravel-breeze), a basic implementation of all of Laravel's [authentication features](https://laravel.com/docs/10.x/authentication).
diff --git a/apps/docs/content/guides/getting-started/quickstarts/sveltekit.mdx b/apps/docs/content/guides/getting-started/quickstarts/sveltekit.mdx
index 16fff4527d8..30be6126edc 100644
--- a/apps/docs/content/guides/getting-started/quickstarts/sveltekit.mdx
+++ b/apps/docs/content/guides/getting-started/quickstarts/sveltekit.mdx
@@ -112,7 +112,7 @@ hideToc: true
- Use `load` method to fetch the data server-side and display the query results as a simple list.
+ Use `load` method to fetch the data server-side and display the query results as a list.
Create `+page.server.js` file in the `src/routes` directory with the following code.
diff --git a/apps/docs/content/guides/getting-started/tutorials/with-redwoodjs.mdx b/apps/docs/content/guides/getting-started/tutorials/with-redwoodjs.mdx
index 18f4af41521..36482c6e839 100644
--- a/apps/docs/content/guides/getting-started/tutorials/with-redwoodjs.mdx
+++ b/apps/docs/content/guides/getting-started/tutorials/with-redwoodjs.mdx
@@ -28,7 +28,7 @@ Important: When this guide refers to "API," that means the Supabase API and when
The **`api side`** is an implementation of a GraphQL API. The business logic is organized into "services" that represent their own internal API and can be called both from external GraphQL requests and other internal services.
-The **`web side`** is built with React. Redwood's router makes it simple to map URL paths to React "Page" components (and automatically code-split your app on each route).
+The **`web side`** is built with React. Redwood's router lets you map URL paths to React "Page" components (and automatically code-split your app on each route).
Pages may contain a "Layout" component to wrap content. They also contain "Cells" and regular React components.
Cells allow you to declaratively manage the lifecycle of a component that fetches and displays data.
@@ -249,8 +249,8 @@ Now, update the `Auth.js` component to contain:
<$CodeTabs>
```jsx name=/web/src/components/Auth/Auth.js
-import { useState } from 'react'
import { useAuth } from '@redwoodjs/auth'
+import { useState } from 'react'
const Auth = () => {
const { logIn } = useAuth()
@@ -326,8 +326,8 @@ And then update the file to contain:
<$CodeTabs>
```jsx name=web/src/components/Account/Account.js
-import { useState, useEffect } from 'react'
import { useAuth } from '@redwoodjs/auth'
+import { useEffect, useState } from 'react'
const Account = () => {
const { client: supabase, currentUser, logOut } = useAuth()
@@ -464,7 +464,6 @@ With all the components in place, update your `HomePage` page to use them:
```jsx name=web/src/pages/HomePage/HomePage.js
import { useAuth } from '@redwoodjs/auth'
import { MetaTags } from '@redwoodjs/web'
-
import Account from 'src/components/Account'
import Auth from 'src/components/Auth'
@@ -511,8 +510,8 @@ Now, update your Avatar component to contain the following widget:
<$CodeTabs>
```jsx name=web/src/components/Avatar/Avatar.js
-import { useEffect, useState } from 'react'
import { useAuth } from '@redwoodjs/auth'
+import { useEffect, useState } from 'react'
const Avatar = ({ url, size, onUpload }) => {
const { client: supabase } = useAuth()
diff --git a/apps/docs/content/guides/integrations/partner-integration-guide.mdx b/apps/docs/content/guides/integrations/partner-integration-guide.mdx
index 74ff3e28eeb..3cf4bd56726 100644
--- a/apps/docs/content/guides/integrations/partner-integration-guide.mdx
+++ b/apps/docs/content/guides/integrations/partner-integration-guide.mdx
@@ -9,12 +9,12 @@ This guide assumes you have already followed [the Build a Supabase Integration g
When a Supabase user clicks the **Install Integration** button in the Dashboard, they are redirected to your system to begin the OAuth flow. You can implement this redirect in one of two ways:
-- **[Simple redirect](#method-1-simple-redirect)**: Easier to build, but your system cannot verify that the incoming user was sent by Supabase.
+- **[Redirect](#method-1-redirect)**: Easier to build, but your system cannot verify that the incoming user was sent by Supabase.
- **[Signed redirect](#method-2-signed-redirect)**: More work to build, but cryptographically verifies that the redirect originated from Supabase. **Recommended for production integrations.**
Pick the method that fits your security requirements, then follow the matching section below.
-## Method 1: Simple redirect
+## Method 1: Redirect
In this method, you implement a single `GET` endpoint. Supabase redirects the user to this endpoint when they click **Install Integration**, and your endpoint kicks off the OAuth flow.
diff --git a/apps/docs/content/guides/integrations/vercel-marketplace.mdx b/apps/docs/content/guides/integrations/vercel-marketplace.mdx
index 8471fd1cdd4..35c554d1695 100644
--- a/apps/docs/content/guides/integrations/vercel-marketplace.mdx
+++ b/apps/docs/content/guides/integrations/vercel-marketplace.mdx
@@ -58,7 +58,7 @@ These variables ensure your applications can connect securely to the database an
## Studio support
-Accessing Supabase Studio is simple through the Vercel dashboard. You can open Supabase Studio from either the Integration installation page or the Vercel Storage page.
+Open Supabase Studio from the Vercel dashboard. You can access it from either the Integration installation page or the Vercel Storage page.
Depending on your entry point, you'll either land on the Supabase dashboard homepage or be redirected to the corresponding Supabase Project.
Supabase Studio provides tools such as:
diff --git a/apps/docs/content/guides/local-development/cli/testing-and-linting.mdx b/apps/docs/content/guides/local-development/cli/testing-and-linting.mdx
index 017961afb7c..2fc83fe1ee9 100644
--- a/apps/docs/content/guides/local-development/cli/testing-and-linting.mdx
+++ b/apps/docs/content/guides/local-development/cli/testing-and-linting.mdx
@@ -44,7 +44,7 @@ By default, Mailpit is available at [localhost:54324](http://localhost:54324) wh
### Going into production
-The "default" email provided by Supabase is only for development purposes. It is [heavily restricted](/docs/guides/platform/going-into-prod#auth-rate-limits) to ensure that it is not used for spam. Before going into production, you must configure your own email provider. This is as simple as enabling a new SMTP credentials in your [project settings](/dashboard/project/_/auth/smtp).
+The "default" email provided by Supabase is only for development purposes. It is [heavily restricted](/docs/guides/platform/going-into-prod#auth-rate-limits) to ensure that it is not used for spam. Before going into production, configure your own email provider by enabling SMTP credentials in your [project settings](/dashboard/project/_/auth/smtp).
## Linting your database
diff --git a/apps/docs/content/guides/local-development/testing/overview.mdx b/apps/docs/content/guides/local-development/testing/overview.mdx
index 8c4624a92a6..9b0e3ac7e09 100644
--- a/apps/docs/content/guides/local-development/testing/overview.mdx
+++ b/apps/docs/content/guides/local-development/testing/overview.mdx
@@ -17,12 +17,12 @@ Testing is a critical part of database development, especially when working with
- Functions and procedures
- Data integrity
-This example demonstrates setting up and testing RLS policies for a simple todo application:
+This example demonstrates setting up and testing RLS policies for a basic todo application:
1. Create a test table with RLS enabled:
```sql
- -- Create a simple todos table
+ -- Create a todos table
create table todos (
id uuid primary key default gen_random_uuid(),
task text not null,
diff --git a/apps/docs/content/guides/local-development/testing/pgtap-extended.mdx b/apps/docs/content/guides/local-development/testing/pgtap-extended.mdx
index b7bbefecbea..6401ab340f4 100644
--- a/apps/docs/content/guides/local-development/testing/pgtap-extended.mdx
+++ b/apps/docs/content/guides/local-development/testing/pgtap-extended.mdx
@@ -83,7 +83,7 @@ The test helpers package provides several advantages over writing raw pgTAP test
## Schema-wide Row Level Security testing
-When working with Row Level Security, it's crucial to ensure that RLS is enabled on all tables that need it. Create a simple test to verify RLS is enabled across an entire schema:
+When working with Row Level Security, it's crucial to ensure that RLS is enabled on all tables that need it. Create a basic test to verify RLS is enabled across an entire schema:
```sql
begin;
@@ -112,7 +112,7 @@ This setup file should contain:
1. All shared extensions and dependencies
2. Common test utilities
-3. A simple always green test to verify the setup
+3. A basic always-green test to verify the setup
Here's an example setup file:
diff --git a/apps/docs/content/guides/platform.mdx b/apps/docs/content/guides/platform.mdx
index f4c58fe84a0..3953d8a1862 100644
--- a/apps/docs/content/guides/platform.mdx
+++ b/apps/docs/content/guides/platform.mdx
@@ -5,7 +5,7 @@ description: 'Getting started with the Supabase Platform.'
sidebar_label: 'Overview'
---
-Supabase is a hosted platform which makes it very simple to get started without needing to manage any infrastructure.
+Supabase is a hosted platform that allows you to get started without needing to manage any infrastructure.
Visit [supabase.com/dashboard](/dashboard) and sign in to start creating projects.
diff --git a/apps/docs/content/guides/realtime/broadcast.mdx b/apps/docs/content/guides/realtime/broadcast.mdx
index 6714da11eca..41dc5b96aea 100644
--- a/apps/docs/content/guides/realtime/broadcast.mdx
+++ b/apps/docs/content/guides/realtime/broadcast.mdx
@@ -153,7 +153,7 @@ Binary payloads (`ArrayBuffer` / `ArrayBufferView`) are received automatically f
// Join a room/topic. Can be anything except for 'realtime'.
const myChannel = supabase.channel('test-channel')
- // Simple function to log any messages we receive
+ // Function to log any messages we receive
function messageReceived(payload) {
console.log(payload)
}
@@ -176,7 +176,7 @@ Binary payloads (`ArrayBuffer` / `ArrayBufferView`) are received automatically f
```dart
final myChannel = supabase.channel('test-channel');
- // Simple function to log any messages we receive
+ // Log any messages we receive
void messageReceived(payload) {
print(payload);
}
@@ -241,7 +241,7 @@ Binary payloads (`ArrayBuffer` / `ArrayBufferView`) are received automatically f
# Join a room/topic. Can be anything except for 'realtime'.
my_channel = supabase.channel('test-channel')
- # Simple function to log any messages we receive
+ # Function to log any messages we receive
def message_received(payload):
print(f"Broadcast received: {payload}")
diff --git a/apps/docs/content/guides/realtime/protocol.mdx b/apps/docs/content/guides/realtime/protocol.mdx
index 5170749dfc2..05c524e642b 100644
--- a/apps/docs/content/guides/realtime/protocol.mdx
+++ b/apps/docs/content/guides/realtime/protocol.mdx
@@ -35,7 +35,7 @@ Messages can be serialized in different formats. The Realtime protocol supports
## 1.0.0
-Version 1.0.0 is extremely simple. It uses JSON as the serialization format for messages. The underlying WebSocket messages are all text frames.
+Version 1.0.0 is minimal. It uses JSON as the serialization format for messages. The underlying WebSocket messages are all text frames.
Messages contain the following fields:
diff --git a/apps/docs/content/guides/realtime/subscribing-to-database-changes.mdx b/apps/docs/content/guides/realtime/subscribing-to-database-changes.mdx
index 9984e94d6c2..a32e5609e26 100644
--- a/apps/docs/content/guides/realtime/subscribing-to-database-changes.mdx
+++ b/apps/docs/content/guides/realtime/subscribing-to-database-changes.mdx
@@ -73,6 +73,7 @@ Finally, on the client side, listen to the topic `topic:` to receive
```js
import { createClient } from '@supabase/supabase-js'
+
const supabase = createClient('your_project_url', 'your_supabase_api_key')
// ---cut---
@@ -90,7 +91,7 @@ const changes = supabase
## Using Postgres Changes
-Postgres Changes are simple to use, but have some [limitations](/docs/guides/realtime/postgres-changes#limitations) as your application scales. We recommend using Broadcast for most use cases.
+Postgres Changes require minimal setup, but have some [limitations](/docs/guides/realtime/postgres-changes#limitations) as your application scales. We recommend using Broadcast for most use cases.
-
-
-
-
Getting Started
+
+
- Getting Started
++ Set up and connect a database in just a few minutes. +
- Set up and connect a database in just a few minutes. -
From c54168842b36835e50299ef8fd3700371b239e6a Mon Sep 17 00:00:00 2001
From: Matt Rossman <22670878+mattrossman@users.noreply.github.com>
Date: Tue, 16 Jun 2026 17:20:06 -0400
Subject: [PATCH 025/488] fix(assistant): prevent parallel approval-required
tool calls (#47008)
Addresses the issue of parallel tool approvals freezing Assistant and
causing UX ambiguity around what happens if only part of multiple
dependent invocations is approved.
Two layers at which this is addressed:
1. Tightens prompt to clarify approval tools must be issued one per
step, not in parallel.
2. In case something slips past the prompt, this also auto-denies all
but the first `approval-required` tool call when the model issues
multiple in the same step, so the model is forced to reissue them
sequentially.
**Demo**
The following chats demo me explicitly asking Assistant to run those
approval-gated tools in parallel, and the Assistant correctly invokes
them sequentially instead.
| Parallel `execute_sql` request | Parallel `deploy_edge_function`
request |
|--------|--------|
| 
| 
|
As shown in [this
trace](https://www.braintrust.dev/app/supabase.io/p/Assistant/trace?object_type=project_logs&object_id=5a8d02e5-b3b6-40cc-ba76-ecee286478f4&r=a3a37857-95df-4a95-a5a8-818ea305b2a5&s=a3a37857-95df-4a95-a5a8-818ea305b2a5),
parallel tool calls are still allowed for context gathering tools that
don't require approval:
Closes AI-803
## Summary by CodeRabbit
* **Improvements**
* Approval-required operations are now processed sequentially rather
than in parallel within the AI Assistant.
* **Tests**
* Added comprehensive test coverage for the parallel approval prevention
logic.
---
.../ui/AIAssistantPanel/AIAssistant.tsx | 13 ++++
apps/studio/lib/ai/message-utils.test.ts | 78 ++++++++++++++++++-
apps/studio/lib/ai/message-utils.ts | 16 +++-
apps/studio/lib/ai/prompts.ts | 2 +-
4 files changed, 105 insertions(+), 4 deletions(-)
diff --git a/apps/studio/components/ui/AIAssistantPanel/AIAssistant.tsx b/apps/studio/components/ui/AIAssistantPanel/AIAssistant.tsx
index 2184f94a8e0..6b8848e44d7 100644
--- a/apps/studio/components/ui/AIAssistantPanel/AIAssistant.tsx
+++ b/apps/studio/components/ui/AIAssistantPanel/AIAssistant.tsx
@@ -39,6 +39,7 @@ import { useLocalStorageQuery } from '@/hooks/misc/useLocalStorage'
import { useOrgAiOptInLevel } from '@/hooks/misc/useOrgOptedIntoAi'
import { useSelectedOrganizationQuery } from '@/hooks/misc/useSelectedOrganization'
import { useSelectedProjectQuery } from '@/hooks/misc/useSelectedProject'
+import { getParallelApprovalIdsToReject } from '@/lib/ai/message-utils'
import {
DEFAULT_ASSISTANT_BASE_MODEL_ID,
defaultAssistantModelId,
@@ -366,6 +367,18 @@ export const AIAssistant = ({ className }: AIAssistantProps) => {
}
}, [isResubmitting, chatStatus, error])
+ useEffect(() => {
+ // Approval-required tools can't run in parallel. Auto-deny extras so the model reissues them sequentially.
+ for (const id of getParallelApprovalIdsToReject(chatMessages)) {
+ addToolApprovalResponse?.({
+ id,
+ approved: false,
+ reason:
+ 'Only one approval-required tool call is allowed per turn. Please reissue this tool call after the current one completes.',
+ })
+ }
+ }, [chatMessages, addToolApprovalResponse])
+
useEffect(() => {
setValue(snap.initialInput || '')
if (inputRef.current && snap.initialInput) {
diff --git a/apps/studio/lib/ai/message-utils.test.ts b/apps/studio/lib/ai/message-utils.test.ts
index 34502f43d2a..0125996ddc7 100644
--- a/apps/studio/lib/ai/message-utils.test.ts
+++ b/apps/studio/lib/ai/message-utils.test.ts
@@ -1,7 +1,81 @@
-import type { UIMessage } from 'ai'
+import type { DynamicToolUIPart, UIMessage } from 'ai'
import { describe, expect, it } from 'vitest'
-import { prepareMessagesForAPI } from './message-utils'
+import { getParallelApprovalIdsToReject, prepareMessagesForAPI } from './message-utils'
+
+const makeApprovalPart = (id: string): DynamicToolUIPart => ({
+ type: 'dynamic-tool',
+ toolName: 'test_tool',
+ toolCallId: id,
+ state: 'approval-requested',
+ input: {},
+ approval: { id },
+})
+
+const makeResultPart = (id: string): DynamicToolUIPart => ({
+ type: 'dynamic-tool',
+ toolName: 'test_tool',
+ toolCallId: id,
+ state: 'output-available',
+ input: {},
+ output: {},
+})
+
+describe('getParallelApprovalIdsToReject', () => {
+ it('returns [] for empty messages', () => {
+ expect(getParallelApprovalIdsToReject([])).toEqual([])
+ })
+
+ it('returns [] when there are no assistant messages', () => {
+ const messages: UIMessage[] = [{ id: '1', role: 'user', parts: [] }]
+ expect(getParallelApprovalIdsToReject(messages)).toEqual([])
+ })
+
+ it('returns [] when last assistant message has no pending approvals', () => {
+ const messages: UIMessage[] = [{ id: '1', role: 'assistant', parts: [makeResultPart('r1')] }]
+ expect(getParallelApprovalIdsToReject(messages)).toEqual([])
+ })
+
+ it('returns [] when there is only one pending approval', () => {
+ const messages: UIMessage[] = [{ id: '1', role: 'assistant', parts: [makeApprovalPart('a1')] }]
+ expect(getParallelApprovalIdsToReject(messages)).toEqual([])
+ })
+
+ it('returns all but the first id when there are multiple pending approvals', () => {
+ const messages: UIMessage[] = [
+ {
+ id: '1',
+ role: 'assistant',
+ parts: [makeApprovalPart('a1'), makeApprovalPart('a2'), makeApprovalPart('a3')],
+ },
+ ]
+ expect(getParallelApprovalIdsToReject(messages)).toEqual(['a2', 'a3'])
+ })
+
+ it('only inspects the last assistant message', () => {
+ const messages: UIMessage[] = [
+ {
+ id: '1',
+ role: 'assistant',
+ parts: [makeApprovalPart('old1'), makeApprovalPart('old2')],
+ },
+ { id: '2', role: 'user', parts: [] },
+ { id: '3', role: 'assistant', parts: [makeApprovalPart('new1')] },
+ ]
+ expect(getParallelApprovalIdsToReject(messages)).toEqual([])
+ })
+
+ it('ignores non-approval tool parts', () => {
+ const messages: UIMessage[] = [
+ {
+ id: '1',
+ role: 'assistant',
+ parts: [makeResultPart('r1'), makeApprovalPart('a1'), makeApprovalPart('a2')],
+ },
+ ]
+ expect(getParallelApprovalIdsToReject(messages)).toEqual(['a2'])
+ })
+})
describe('prepareMessagesForAPI', () => {
it('should limit messages to last 7 entries', () => {
diff --git a/apps/studio/lib/ai/message-utils.ts b/apps/studio/lib/ai/message-utils.ts
index 2b0cbd62924..d04e25b5c1d 100644
--- a/apps/studio/lib/ai/message-utils.ts
+++ b/apps/studio/lib/ai/message-utils.ts
@@ -1,4 +1,4 @@
-import type { UIMessage } from 'ai'
+import { isToolUIPart, type UIMessage } from 'ai'
/**
* Prepares messages for API transmission by cleaning and limiting history
@@ -23,3 +23,17 @@ export function prepareMessagesForAPI(messages: UIMessage[]): UIMessage[] {
return cleanedMessages
}
+
+/**
+ * Returns approval IDs to auto-deny when the model issues multiple approval-required
+ * tool calls in the same turn — all but the first, so the model reissues them sequentially.
+ */
+export function getParallelApprovalIdsToReject(messages: UIMessage[]): string[] {
+ const lastMessage = messages.findLast((m) => m.role === 'assistant')
+ if (!lastMessage) return []
+
+ const pendingIds = (lastMessage.parts ?? []).flatMap((part) =>
+ isToolUIPart(part) && part.state === 'approval-requested' ? [part.approval.id] : []
+ )
+ return pendingIds.slice(1)
+}
diff --git a/apps/studio/lib/ai/prompts.ts b/apps/studio/lib/ai/prompts.ts
index 09f71fb4f5d..81c6f0435f6 100644
--- a/apps/studio/lib/ai/prompts.ts
+++ b/apps/studio/lib/ai/prompts.ts
@@ -733,7 +733,7 @@ export const CHAT_PROMPT = `
- On execution error, explain succinctly and attempt to correct if possible, validating each outcome briefly (1–2 lines) after execution.
- If a user skips execution, acknowledge and suggest alternatives.
- Use markdown code blocks (\`\`\`sql\`\`\`) for illustrative SQL only if requested by the user or when providing non-executable examples.
-- Execute multiple queries separately via \`execute_sql\` and briefly validate outcomes.
+- Never call \`execute_sql\` or \`deploy_edge_function\` in parallel within the same step. Each requires user approval, so issue one per step and wait for its result before calling the next.
- After execution, summarize outcomes concisely without duplicating results, as the client will present these.
## Edge Functions
- Deploy Edge Functions by calling \`deploy_edge_function\` directly with \`name\` and \`code\`; the client handles confirmation and result presentation.
From 608040b8cb3f553d142d43d3f91eb6de89624559 Mon Sep 17 00:00:00 2001
From: Miranda Limonczenko
Date: Tue, 16 Jun 2026 14:45:55 -0700
Subject: [PATCH 026/488] chore(docs) Resolve 'simple' style warnings where
applicable (#46966)
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Contributes to DOCS-1052
## I have read the
[CONTRIBUTING.md](https://github.com/supabase/supabase/blob/master/CONTRIBUTING.md)
file.
YES
## What kind of change does this PR introduce?
Resolves MDX linting errors related to "simple" where it applies.
There was a couple cases that did not apply. For example, a product with
"Simple" in the name.
These changes are made in context, either by removing or using a more
descriptive synonym like "minimal" or "basic".
## Tophatting
1. Read each of the diffs.
2. See that the text still makes sense in context.
For extra due diligence, you can run `pnpm lint:mdx` locally and see the
'simple' errors that remain and whether they are worth addressing.
## Summary by CodeRabbit
## Summary by CodeRabbit
* **Documentation**
* Updated many guide, tutorial, and troubleshooting pages with clearer
“basic”/“minimal” wording across setup steps, local testing
instructions, security cautions, and RLS guidance.
* Refined headings, example descriptions, and inline comments for
consistency (including deployment, MCP, metrics API, and search/function
phrasing).
* Improved readability with small snippet formatting tweaks (whitespace
plus import/comment ordering) and added a self-hosting debugging note
for Envoy admin endpoints via a short-lived `curl` container.
---------
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
Co-authored-by: Chris Chinchilla
Co-authored-by: Nik Richers
---
apps/docs/content/_partials/database_setup.mdx | 2 +-
apps/docs/content/_partials/kotlin_project_setup.mdx | 2 +-
apps/docs/content/_partials/metrics_access.mdx | 2 +-
apps/docs/content/guides/ai-tools/byo-mcp.mdx | 6 ++++--
apps/docs/content/guides/ai.mdx | 8 ++++----
apps/docs/content/guides/ai/engineering-for-scale.mdx | 4 ++--
.../guides/ai/examples/building-chatgpt-plugins.mdx | 2 +-
apps/docs/content/guides/ai/keyword-search.mdx | 2 +-
apps/docs/content/guides/ai/langchain.mdx | 2 +-
apps/docs/content/guides/ai/rag-with-permissions.mdx | 2 +-
apps/docs/content/guides/auth/auth-mfa.mdx | 2 +-
apps/docs/content/guides/auth/auth-mfa/totp.mdx | 2 +-
apps/docs/content/guides/auth/auth-smtp.mdx | 2 +-
apps/docs/content/guides/auth/server-side.mdx | 2 +-
.../connecting-to-postgres/serverless-drivers.mdx | 2 +-
apps/docs/content/guides/database/extensions/http.mdx | 4 ++--
.../docs/content/guides/database/extensions/hypopg.mdx | 2 +-
.../content/guides/database/extensions/postgis.mdx | 4 ++--
.../content/guides/database/extensions/timescaledb.mdx | 2 +-
apps/docs/content/guides/database/functions.mdx | 6 +++---
apps/docs/content/guides/database/partitions.mdx | 2 +-
apps/docs/content/guides/database/postgres/indexes.mdx | 2 +-
apps/docs/content/guides/database/tables.mdx | 2 +-
apps/docs/content/guides/database/testing.mdx | 2 +-
apps/docs/content/guides/deployment.mdx | 6 +++---
.../guides/deployment/shared-responsibility-model.mdx | 2 +-
apps/docs/content/guides/functions.mdx | 2 +-
apps/docs/content/guides/functions/architecture.mdx | 2 +-
.../content/guides/functions/examples/discord-bot.mdx | 5 +++--
.../guides/functions/examples/mcp-server-mcp-lite.mdx | 2 +-
.../content/guides/functions/recursive-functions.mdx | 4 ++--
apps/docs/content/guides/functions/routing.mdx | 2 +-
apps/docs/content/guides/functions/unit-test.mdx | 2 +-
apps/docs/content/guides/functions/wasm.mdx | 2 +-
apps/docs/content/guides/getting-started/api-keys.mdx | 2 +-
.../content/guides/getting-started/architecture.mdx | 4 ++--
apps/docs/content/guides/getting-started/features.mdx | 2 +-
.../guides/getting-started/quickstarts/laravel.mdx | 2 +-
.../guides/getting-started/quickstarts/sveltekit.mdx | 2 +-
.../getting-started/tutorials/with-redwoodjs.mdx | 9 ++++-----
.../guides/integrations/partner-integration-guide.mdx | 4 ++--
.../content/guides/integrations/vercel-marketplace.mdx | 2 +-
.../local-development/cli/testing-and-linting.mdx | 2 +-
.../guides/local-development/testing/overview.mdx | 4 ++--
.../local-development/testing/pgtap-extended.mdx | 4 ++--
apps/docs/content/guides/platform.mdx | 2 +-
apps/docs/content/guides/realtime/broadcast.mdx | 6 +++---
apps/docs/content/guides/realtime/protocol.mdx | 2 +-
.../realtime/subscribing-to-database-changes.mdx | 5 ++++-
apps/docs/content/guides/resources/glossary.mdx | 2 +-
apps/docs/content/guides/security.mdx | 2 +-
.../content/guides/self-hosting/self-hosted-envoy.mdx | 2 +-
.../guides/storage/uploads/standard-uploads.mdx | 4 +++-
apps/docs/content/guides/telemetry/logs.mdx | 2 +-
...xceeds-btree-version-4-maximum-for-index-LMmoeU.mdx | 2 +-
...rom-supabase-auth-helpers-to-ssr-package-5NRunM.mdx | 2 +-
apps/docs/content/troubleshooting/http-api-issues.mdx | 2 +-
...esponse-or-zgotmplz-in-magic-link-emails-433665.mdx | 2 +-
.../troubleshooting/prisma-error-management-Cm5P_o.mdx | 2 +-
.../troubleshooting/realtime-heartbeat-messages.mdx | 10 +++++-----
.../troubleshooting/soft-deletes-with-supabase-js.mdx | 2 +-
61 files changed, 95 insertions(+), 88 deletions(-)
diff --git a/apps/docs/content/_partials/database_setup.mdx b/apps/docs/content/_partials/database_setup.mdx
index 92112438ddc..09cac33af3c 100644
--- a/apps/docs/content/_partials/database_setup.mdx
+++ b/apps/docs/content/_partials/database_setup.mdx
@@ -1,6 +1,6 @@
## Project setup
-Let's create a new Postgres database. This is as simple as starting a new Project in Supabase:
+To create a new Postgres database, start a new Project in Supabase:
1. [Create a new project](https://database.new/) in the Supabase dashboard.
1. Enter your project details. Remember to store your password somewhere safe.
diff --git a/apps/docs/content/_partials/kotlin_project_setup.mdx b/apps/docs/content/_partials/kotlin_project_setup.mdx
index 1f32521eefd..91b95ad86ec 100644
--- a/apps/docs/content/_partials/kotlin_project_setup.mdx
+++ b/apps/docs/content/_partials/kotlin_project_setup.mdx
@@ -1,6 +1,6 @@
## Project setup
-Before we start building we're going to set up our Database and API. This is as simple as starting a new Project in Supabase and then creating a "schema" inside the database.
+Before building, you must set up your Database and API with a new Project in Supabase and then create a "schema" inside the database.
### Create a project
diff --git a/apps/docs/content/_partials/metrics_access.mdx b/apps/docs/content/_partials/metrics_access.mdx
index 853dcaac14a..2aa32d58aee 100644
--- a/apps/docs/content/_partials/metrics_access.mdx
+++ b/apps/docs/content/_partials/metrics_access.mdx
@@ -25,7 +25,7 @@ className="rounded-lg border border-foreground/10 bg-surface-100 text-foreground
- **Username**: `service_role`
- **Password**: a **Secret API key** (`sb_secret_...`). You can create/copy it in [**Project Settings → API Keys**](/dashboard/project/_/settings/api-keys). For more context, see [Understanding API keys](/docs/guides/getting-started/api-keys).
- Testing locally is as simple as running `curl` with your Secret API key:
+ To test locally, run `curl` with your Secret API key:
```bash
curl /customer/v1/privileged/metrics \
diff --git a/apps/docs/content/guides/ai-tools/byo-mcp.mdx b/apps/docs/content/guides/ai-tools/byo-mcp.mdx
index 88e708a8c4b..2df8f11ed23 100644
--- a/apps/docs/content/guides/ai-tools/byo-mcp.mdx
+++ b/apps/docs/content/guides/ai-tools/byo-mcp.mdx
@@ -75,7 +75,7 @@ const server = new McpServer({
version: '0.1.0',
})
-// Register a simple addition tool
+// Register an addition tool
server.registerTool(
'add',
{
@@ -218,7 +218,9 @@ After this step, you have a fully deployed MCP server accessible from anywhere.
You can find ready-to-use MCP server implementations here:
-- [Simple MCP server](https://github.com/supabase/supabase/tree/master/examples/edge-functions/supabase/functions/mcp/simple-mcp-server) - Basic unauthenticated example
+{/* supa-mdx-lint-disable-next-line Rule004ExcludeWords */}
+
+- [Simple MCP server](https://github.com/supabase/supabase/tree/master/examples/edge-functions/supabase/functions/mcp/simple-mcp-server) - Unauthenticated example
## Resources
diff --git a/apps/docs/content/guides/ai.mdx b/apps/docs/content/guides/ai.mdx
index 4fb8c15b66c..5226d8849aa 100644
--- a/apps/docs/content/guides/ai.mdx
+++ b/apps/docs/content/guides/ai.mdx
@@ -109,8 +109,8 @@ Check out all of the AI [templates and examples](https://github.com/supabase/sup
- OpenAI is an AI research and deployment company. Supabase provides a simple way to use
- OpenAI in your applications.
+ OpenAI is an AI research and deployment company. Supabase provides a way to use OpenAI in
+ your applications.
@@ -125,8 +125,8 @@ Check out all of the AI [templates and examples](https://github.com/supabase/sup
- Hugging Face is an open-source provider of NLP technologies. Supabase provides a simple way
- to use Hugging Face's models in your applications.
+ Hugging Face is an open-source provider of NLP technologies. Supabase provides a way to use
+ Hugging Face's models in your applications.
diff --git a/apps/docs/content/guides/ai/engineering-for-scale.mdx b/apps/docs/content/guides/ai/engineering-for-scale.mdx
index 55e8990507d..a9c74970bd7 100644
--- a/apps/docs/content/guides/ai/engineering-for-scale.mdx
+++ b/apps/docs/content/guides/ai/engineering-for-scale.mdx
@@ -8,9 +8,9 @@ sidebar_label: 'Engineering for Scale'
Content sources for vectors can be extremely large. As you grow you should run your Vector workloads across several secondary databases (sometimes called "pods"), which allows each collection to scale independently.
-## Simple workloads
+## Small workloads [#simple-workloads]
-For small workloads, it's typical to store your data in a single database.
+For small workloads, you can typically store your data in a single database.
If you've used [Vecs](/docs/guides/ai/vecs-python-client) to create 3 different collections, you can expose collections to your web or mobile application using [views](/docs/guides/database/tables#views):
diff --git a/apps/docs/content/guides/ai/examples/building-chatgpt-plugins.mdx b/apps/docs/content/guides/ai/examples/building-chatgpt-plugins.mdx
index b6dfa676b9d..8d6bc5eb3ee 100644
--- a/apps/docs/content/guides/ai/examples/building-chatgpt-plugins.mdx
+++ b/apps/docs/content/guides/ai/examples/building-chatgpt-plugins.mdx
@@ -20,7 +20,7 @@ It allows ChatGPT to dynamically pull relevant information into conversations fr
## Example: Chat with Postgres docs
-Let’s build an example where we can “ask ChatGPT questions” about the Postgres documentation. Although ChatGPT already knows about the Postgres documentation because it is publicly available, this is a simple example which demonstrates how to work with PDF files.
+Let’s build an example where we can “ask ChatGPT questions” about the Postgres documentation. Although ChatGPT already knows about the Postgres documentation because it is publicly available, this is a basic example which demonstrates how to work with PDF files.
This plugin requires several steps:
diff --git a/apps/docs/content/guides/ai/keyword-search.mdx b/apps/docs/content/guides/ai/keyword-search.mdx
index 9ee03877831..643fa08025f 100644
--- a/apps/docs/content/guides/ai/keyword-search.mdx
+++ b/apps/docs/content/guides/ai/keyword-search.mdx
@@ -8,7 +8,7 @@ sidebar_label: 'Keyword search'
Keyword search involves locating documents or records that contain specific words or phrases, primarily based on the exact match between the search terms and the text within the data. It differs from [semantic search](/docs/guides/ai/semantic-search), which interprets the meaning behind the query to provide results that are contextually related, even if the exact words aren't present in the text. Semantic search considers synonyms, intent, and natural language nuances to provide a more nuanced approach to information retrieval.
-In Postgres, keyword search is implemented using [full-text search](/docs/guides/database/full-text-search). It supports indexing and text analysis for data retrieval, focusing on records that match the search criteria. Postgres' full-text search extends beyond simple keyword matching to address linguistic nuances, making it effective for applications that require precise text queries.
+In Postgres, keyword search is implemented using [full-text search](/docs/guides/database/full-text-search). It supports indexing and text analysis for data retrieval, focusing on records that match the search criteria. Postgres' full-text search extends beyond keyword matching to address linguistic nuances, making it effective for applications that require precise text queries.
## When and why to use keyword search
diff --git a/apps/docs/content/guides/ai/langchain.mdx b/apps/docs/content/guides/ai/langchain.mdx
index b089cb4ab5e..09cf1c570fa 100644
--- a/apps/docs/content/guides/ai/langchain.mdx
+++ b/apps/docs/content/guides/ai/langchain.mdx
@@ -108,7 +108,7 @@ export const run = async () => {
}
```
-### Simple metadata filtering
+### Basic metadata filtering [#simple-metadata-filtering]
Given the above `match_documents` Postgres function, you can also pass a filter parameter to only return documents with a specific metadata field value. This filter parameter is a JSON object, and the `match_documents` function will use the Postgres JSONB Containment operator `@>` to filter documents by the metadata field values you specify. See details on the [Postgres JSONB Containment operator](https://www.postgresql.org/docs/current/datatype-json.html#JSON-CONTAINMENT) for more information.
diff --git a/apps/docs/content/guides/ai/rag-with-permissions.mdx b/apps/docs/content/guides/ai/rag-with-permissions.mdx
index 08c8ca7b021..4b2df595dce 100644
--- a/apps/docs/content/guides/ai/rag-with-permissions.mdx
+++ b/apps/docs/content/guides/ai/rag-with-permissions.mdx
@@ -231,7 +231,7 @@ order by document_sections.embedding <#> embedding;
{/* supa-mdx-lint-disable-next-line Rule004ExcludeWords */}
-You might be tempted to discard RLS completely and simply filter by user within the `where` clause. Though this will work, we recommend RLS as a general best practice since RLS is always applied even as new queries and application logic is introduced in the future.
+You might be tempted to discard RLS completely and filter by user within the `where` clause. Though this will work, we recommend RLS as a general best practice since RLS is always applied even as new queries and application logic is introduced in the future.
diff --git a/apps/docs/content/guides/auth/auth-mfa.mdx b/apps/docs/content/guides/auth/auth-mfa.mdx
index 1cb3576ef18..542884c5aa8 100644
--- a/apps/docs/content/guides/auth/auth-mfa.mdx
+++ b/apps/docs/content/guides/auth/auth-mfa.mdx
@@ -127,7 +127,7 @@ Unenrolling a factor will downgrade the assurance level from `aal2` to `aal1` on
```tsx
/**
- * UnenrollMFA shows a simple table with the list of factors together with a button to unenroll.
+ * UnenrollMFA shows a table with the list of factors together with a button to unenroll.
* When a user types in the factorId of the factor that they wish to unenroll and clicks unenroll
* the corresponding factor will be unenrolled.
*/
diff --git a/apps/docs/content/guides/auth/auth-mfa/totp.mdx b/apps/docs/content/guides/auth/auth-mfa/totp.mdx
index c645e15f681..c1869fbb097 100644
--- a/apps/docs/content/guides/auth/auth-mfa/totp.mdx
+++ b/apps/docs/content/guides/auth/auth-mfa/totp.mdx
@@ -75,7 +75,7 @@ Below is an example that creates a new `EnrollMFA` component that illustrates th
```tsx
/**
- * EnrollMFA shows a simple enrollment dialog. When shown on screen it calls
+ * EnrollMFA shows an enrollment dialog. When shown on screen it calls
* the `enroll` API. Each time a user clicks the Enable button it calls the
* `challenge` and `verify` APIs to check if the code provided by the user is
* valid.
diff --git a/apps/docs/content/guides/auth/auth-smtp.mdx b/apps/docs/content/guides/auth/auth-smtp.mdx
index 2e4d9fefd33..b43e261bda7 100644
--- a/apps/docs/content/guides/auth/auth-smtp.mdx
+++ b/apps/docs/content/guides/auth/auth-smtp.mdx
@@ -13,7 +13,7 @@ If you're using Supabase Auth with the following configuration:
You will need to set up a custom SMTP server to handle the delivery of messages to your users.
-To get you started and let you explore and set up email message templates for your application, Supabase provides a simple SMTP server for all projects. This server imposes a few important restrictions and is not meant for production use.
+To get you started and let you explore and set up email message templates for your application, Supabase provides an SMTP server for all projects. This server imposes a few important restrictions and is not meant for production use.
**Send messages only to pre-authorized addresses.**
diff --git a/apps/docs/content/guides/auth/server-side.mdx b/apps/docs/content/guides/auth/server-side.mdx
index 782db4bc501..81ae770cd4a 100644
--- a/apps/docs/content/guides/auth/server-side.mdx
+++ b/apps/docs/content/guides/auth/server-side.mdx
@@ -15,7 +15,7 @@ Make sure to use the PKCE flow instructions where those differ from the implicit
## `@supabase/ssr`
-We have developed an [`@supabase/ssr`](https://www.npmjs.com/package/@supabase/ssr) package to make setting up the Supabase client as simple as possible. This package is currently in beta. Adoption is recommended but be aware that the API is still unstable and may have breaking changes in the future.
+We have developed an [`@supabase/ssr`](https://www.npmjs.com/package/@supabase/ssr) package for setting up the Supabase client. This package is currently in beta. Adoption is recommended but be aware that the API is still unstable and may have breaking changes in the future.
## Framework quickstarts
diff --git a/apps/docs/content/guides/database/connecting-to-postgres/serverless-drivers.mdx b/apps/docs/content/guides/database/connecting-to-postgres/serverless-drivers.mdx
index 24591674340..87a78a6f926 100644
--- a/apps/docs/content/guides/database/connecting-to-postgres/serverless-drivers.mdx
+++ b/apps/docs/content/guides/database/connecting-to-postgres/serverless-drivers.mdx
@@ -35,7 +35,7 @@ Choose one of these Vercel Deploy Templates which use our [Vercel Deploy Integra
passHref
>
- Simple Next.js template that uses Supabase as the database and Kysely as the query builder.
+ Basic Next.js template that uses Supabase as the database and Kysely as the query builder.
diff --git a/apps/docs/content/guides/database/extensions/http.mdx b/apps/docs/content/guides/database/extensions/http.mdx
index ed4052e62e0..f987f35493c 100644
--- a/apps/docs/content/guides/database/extensions/http.mdx
+++ b/apps/docs/content/guides/database/extensions/http.mdx
@@ -88,7 +88,7 @@ A successful call to a web URL from the `http` extension returns a record with t
## Examples
-### Simple `GET` example
+### Basic `GET` example [#simple-get-example]
```sql
select
@@ -97,7 +97,7 @@ from
extensions.http_get('https://jsonplaceholder.typicode.com/todos/1');
```
-### Simple `POST` example
+### Basic `POST` example [#simple-post-example]
```sql
select
diff --git a/apps/docs/content/guides/database/extensions/hypopg.mdx b/apps/docs/content/guides/database/extensions/hypopg.mdx
index 3a3875ef139..6bea2618227 100644
--- a/apps/docs/content/guides/database/extensions/hypopg.mdx
+++ b/apps/docs/content/guides/database/extensions/hypopg.mdx
@@ -45,7 +45,7 @@ It's good practice to create the extension within a separate schema (like `exten
### Speeding up a query
-Given the following table and a simple query to select from the table by `id`:
+Given the following table and a basic query to select from the table by `id`:
{/* prettier-ignore */}
```sql
diff --git a/apps/docs/content/guides/database/extensions/postgis.mdx b/apps/docs/content/guides/database/extensions/postgis.mdx
index 599f65be591..61b14e05a4e 100644
--- a/apps/docs/content/guides/database/extensions/postgis.mdx
+++ b/apps/docs/content/guides/database/extensions/postgis.mdx
@@ -9,7 +9,7 @@ tocVideo: 'agFsGDJxjwA'
## Overview
-While you may be able to store simple lat/long geographic coordinates as a set of decimals, it does not scale very well when you try to query through a large data set. PostGIS comes with special data types that are efficient, and indexable for high scalability.
+While you may be able to store lat/long geographic coordinates as a set of decimals, it does not scale very well when you try to query through a large data set. PostGIS comes with special data types that are efficient, and indexable for high scalability.
The additional data types that PostGIS provides include [Point](https://postgis.net/docs/using_postgis_dbmanagement.html#Point), [Polygon](https://postgis.net/docs/using_postgis_dbmanagement.html#Polygon), [LineString](https://postgis.net/docs/using_postgis_dbmanagement.html#LineString), and many more to represent different types of geographical data. In this guide, we will mainly focus on how to interact with `Point` type, which represents a single set of latitude and longitude. If you are interested in digging deeper, you can learn more about different data types on the [data management section of PostGIS docs](https://postgis.net/docs/using_postgis_dbmanagement.html).
@@ -47,7 +47,7 @@ drop extension if exists postgis;
## Examples
-Now that we are ready to get started with PostGIS, let’s create a table and see how we can utilize PostGIS for some typical use cases. Let’s imagine we are creating a simple restaurant-searching app.
+Now that we are ready to get started with PostGIS, let’s create a table and see how we can use PostGIS for some typical use cases. Imagine we are creating a basic restaurant-searching app.
Let’s create our table. Each row represents a restaurant with its location stored in `location` column as a `Point` type.
diff --git a/apps/docs/content/guides/database/extensions/timescaledb.mdx b/apps/docs/content/guides/database/extensions/timescaledb.mdx
index a3aa0303646..abea2efc839 100644
--- a/apps/docs/content/guides/database/extensions/timescaledb.mdx
+++ b/apps/docs/content/guides/database/extensions/timescaledb.mdx
@@ -60,7 +60,7 @@ It's good practice to create the extension within a separate schema (like `exten
## Usage
-To demonstrate how `timescaledb` works, let's consider a simple example where we have a table that stores temperature data from different sensors. We will create a table named "temperatures" and store data for two sensors.
+To demonstrate how `timescaledb` works, consider a basic example where we have a table that stores temperature data from different sensors. We will create a table named "temperatures" and store data for two sensors.
First we create a hypertable, which is a virtual table that is partitioned into chunks based on time intervals. The hypertable acts as a proxy for the actual table and makes it easy to query and manage time-series data.
diff --git a/apps/docs/content/guides/database/functions.mdx b/apps/docs/content/guides/database/functions.mdx
index abea38ae77d..5dac1acaa3e 100644
--- a/apps/docs/content/guides/database/functions.mdx
+++ b/apps/docs/content/guides/database/functions.mdx
@@ -30,7 +30,7 @@ and run the SQL queries yourself.
3. Enter the SQL to create or replace your Database function.
4. Click "Run" or cmd+enter (ctrl+enter).
-## Simple functions
+## Basic functions [#simple-functions]
Let's create a basic Database Function which returns a string "hello world".
@@ -53,7 +53,7 @@ At it's most basic a function has the following parts:
2. `returns text`: The type of data that the function returns. If it returns nothing, you can `returns void`.
3. `language sql`: The language used inside the function body. This can also be a procedural language: `plpgsql`, `plpython`, etc.
4. `as $$`: The function wrapper. Anything enclosed inside the `$$` symbols will be part of the function body.
-5. `select 'hello world';`: A simple function body. The final `select` statement inside a function body will be returned if there are no statements following it.
+5. `select 'hello world';`: A basic function body. The final `select` statement inside a function body will be returned if there are no statements following it.
6. `$$;`: The closing symbols of the function wrapper.
@@ -290,7 +290,7 @@ data = supabase.rpc('get_planets').eq('id', 1).execute()
## Passing parameters
-Let's create a Function to insert a new planet into the `planets` table and return the new ID. Note that this time we're using the `plpgsql` language.
+Create a function to insert a new planet into the `planets` table and return the new ID. Note that this time we're using the `plpgsql` language.
```sql
create or replace function add_planet(name text)
diff --git a/apps/docs/content/guides/database/partitions.mdx b/apps/docs/content/guides/database/partitions.mdx
index 9019ea55e34..73e9f3a2903 100644
--- a/apps/docs/content/guides/database/partitions.mdx
+++ b/apps/docs/content/guides/database/partitions.mdx
@@ -105,7 +105,7 @@ There is no real threshold to determine when you should use partitions. Partitio
## Examples
-Here are simple examples for each of the partitioning types in Postgres.
+Here are basic examples for each of the partitioning types in Postgres.
### Range partitioning
diff --git a/apps/docs/content/guides/database/postgres/indexes.mdx b/apps/docs/content/guides/database/postgres/indexes.mdx
index d0b36b77bf0..a4a33e4ab6a 100644
--- a/apps/docs/content/guides/database/postgres/indexes.mdx
+++ b/apps/docs/content/guides/database/postgres/indexes.mdx
@@ -53,7 +53,7 @@ Seq Scan on persons (cost=0.00..22.75 rows=x width=y)
Filter: (age = 32)
```
-To add a simple B-Tree index you can run:
+To add a basic B-Tree index you can run:
```sql
create index idx_persons_age on persons (age);
diff --git a/apps/docs/content/guides/database/tables.mdx b/apps/docs/content/guides/database/tables.mdx
index 4f284bc1dd5..79c3a43e0fa 100644
--- a/apps/docs/content/guides/database/tables.mdx
+++ b/apps/docs/content/guides/database/tables.mdx
@@ -92,7 +92,7 @@ You must define the "data type" when you create a column.
### Data types
-Every column is a predefined type. Postgres provides many [default types](https://www.postgresql.org/docs/current/datatype.html), and you can even design your own (or use extensions) if the default types don't fit your needs. You can use any data type that Postgres supports via the SQL editor. We only support a subset of these in the Table Editor in an effort to keep the experience simple for people with less experience with databases.
+Every column is a predefined type. Postgres provides many [default types](https://www.postgresql.org/docs/current/datatype.html), and you can even design your own (or use extensions) if the default types don't fit your needs. You can use any data type that Postgres supports via the SQL editor. We only support a subset of these in the Table Editor in an effort to keep the experience focused for people with less experience with databases.