The Postgres development platform. Supabase gives you a dedicated Postgres database to build your web, mobile, and AI applications.
TypeScript aialternativeauthdatabasedenoembeddingsexamplefirebasenextjsoauth2pgvectorpostgispostgrespostgresqlpostgrestrealtimesupabasevectorswebsockets
import { useParams } from 'common'
import { useRouter } from 'next/router'
import { useEffect, useEffectEvent } from 'react'
import { parseSqlSnippetSource } from './querySource'
import { createSqlSnippetSkeletonV2 } from './SQLEditor.utils'
import { useSelectedProjectQuery } from '@/hooks/misc/useSelectedProject'
import { useProfile } from '@/lib/profile'
import { wasNeverPersisted } from '@/state/sql-editor/sql-editor-lifecycle'
import { canEditSnippet } from '@/state/sql-editor/sql-editor-rules'
import { useSqlEditorV2StateSnapshot } from '@/state/sql-editor/sql-editor-state'
import { useTabsStateSnapshot } from '@/state/tabs'
/**
* Owns the editing lifecycle of a single SQL snippet: creating the snippet in
* the store on first edit (and routing to its URL), writing changes back to the
* store via `setSql`, and seeding the editor from a `?content=` deep link.
*
* Edits are written to the store synchronously on every change; debouncing the
* actual persistence is the save mechanism's job (see `createSaveMechanism`), so
* the store — and therefore the snippet's dirty status — always reflects the
* latest edit immediately.
*
* Extracted from `MonacoEditor` so that component stays a thin editor shell.
*/
export function useSnippetEditor({ id, snippetName }: { id: string; snippetName: string }) {
const router = useRouter()
const { profile } = useProfile()
const { ref, content, source } = useParams()
const { data: project } = useSelectedProjectQuery()
const snapV2 = useSqlEditorV2StateSnapshot()
const tabsSnap = useTabsStateSnapshot()
const snippet = snapV2.snippets[id]
const disableEdit = !!snippet && !canEditSnippet(snippet.snippet, profile?.id)
function handleEditorChange(value: string | undefined) {
tabsSnap.makeActiveTabPermanent()
if (!id || !value) return
if (!snippet && ref && profile !== undefined && project !== undefined) {
const newSnippet = createSqlSnippetSkeletonV2({
idOverride: id,
name: snippetName,
sql: value,
owner_id: profile?.id,
project_id: project?.id,
// A creation entry (e.g. "New logs query") threads the target backend
// through `/sql/new?source=`; default to a database snippet otherwise.
source: parseSqlSnippetSource(source),
})
snapV2.addSnippet({ projectRef: ref, snippet: newSnippet })
// When the editor was seeded from a `content` deep-link, replace rather
// than push. The caller navigated to `/sql/new?content=...` (a long,
// one-shot URL); replacing collapses it out of history so Back returns to
// the originating page instead of a wasted step that re-seeds the snippet.
if (router.query.content !== undefined) {
router.replace(`/project/${ref}/sql/${newSnippet.id}`, undefined, { shallow: true })
} else {
router.push(`/project/${ref}/sql/${newSnippet.id}`, undefined, { shallow: true })
}
}
// A snippet that has never been persisted needs the snippet/folder lists
// invalidated so it shows up in the sidebar. If `snippet` was undefined at
// render we just created one above (status 'new'), which always qualifies.
const shouldInvalidate = snippet ? wasNeverPersisted(snippet.snippet.status) : true
snapV2.setSql({ id, sql: value, shouldInvalidate })
}
// if an SQL query is passed by the content parameter, set the editor value to its content. This
// is usually used for sending the user to SQL editor from other pages with SQL.
const seedFromContentParam = useEffectEvent(() => {
if (content && content.length > 0) handleEditorChange(content)
})
useEffect(() => {
seedFromContentParam()
}, [])
return { snippet, disableEdit, handleEditorChange }
}