Files
supabase/apps/studio/data/ai/parse-client-code-mutation.ts
Joshen Lim 5f867e5f6c Feature Preview: RLS Tester (#45121)
## Context

Resolves FE-3077
Related discussion: https://github.com/orgs/supabase/discussions/45233

Verifying the correctness of your RLS policies set up has always been a
gap, as highlighted by a number of GitHub discussions like
[here](https://github.com/orgs/supabase/discussions/12269) and
[here](https://github.com/orgs/supabase/discussions/14401). As such,
we're piloting a dedicated UI for RLS testing (using role impersonation
as the base), in which you'll be able to
- Run a SQL query as a user (not logged in / logged in - this is the
role impersonation part)
- See which RLS policies are being evaluated as part of the query
- And hopefully be able to debug which policies are not set up correctly

Changes are currently set as a feature preview - and we'll iterate as we
get feedback from everyone 🙂 🙏

<img width="613" height="957" alt="image"
src="https://github.com/user-attachments/assets/83c37f8a-28fc-43b3-b0ff-e28571d8710c"
/>


<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit

* **New Features**
* RLS Tester: run queries as anon or authenticated users, view inferred
SQL, per-table policy summaries, and data previews of accessible rows.
* UI preview: new RLS Tester preview card and modal with opt-in toggle;
RLS Tester sheet with role/user selector and query editor.
  * SQLEditor: “Explain” tab is always visible.

* **Chores**
* Added supporting API endpoints, background checks for table RLS
status, and a local-storage flag to persist the preview opt-in.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
2026-04-28 15:02:49 +08:00

59 lines
1.7 KiB
TypeScript

import { useMutation } from '@tanstack/react-query'
import { toast } from 'sonner'
import { constructHeaders, fetchHandler } from '@/data/fetchers'
import { BASE_PATH } from '@/lib/constants'
import { ResponseError, UseCustomMutationOptions } from '@/types'
export type ParseClientCodeResponse = {
sql: string | undefined
valid: boolean
}
export type ParseClientCodeVariables = {
code: string
}
export async function generateSqlTitle({ code }: ParseClientCodeVariables) {
try {
const url = `${BASE_PATH}/api/ai/sql/parse-client-code`
const headers = await constructHeaders({ 'Content-Type': 'application/json' })
const response = await fetchHandler(url, {
headers,
method: 'POST',
body: JSON.stringify({ code }),
}).then((res) => res.json())
if (response.error) throw new Error(response.error)
return response as ParseClientCodeResponse
} catch (error) {
throw error
}
}
type ParseClientCodeData = Awaited<ReturnType<typeof generateSqlTitle>>
export const useParseClientCodeMutation = ({
onSuccess,
onError,
...options
}: Omit<
UseCustomMutationOptions<ParseClientCodeData, ResponseError, ParseClientCodeVariables>,
'mutationFn'
> = {}) => {
return useMutation<ParseClientCodeData, ResponseError, ParseClientCodeVariables>({
mutationFn: (vars) => generateSqlTitle(vars),
async onSuccess(data, variables, context) {
await onSuccess?.(data, variables, context)
},
async onError(data, variables, context) {
if (onError === undefined) {
toast.error(`Failed to parse client code: ${data.message}`)
} else {
onError(data, variables, context)
}
},
...options,
})
}