Skip to content

The Postgres development platform. Supabase gives you a dedicated Postgres database to build your web, mobile, and AI applications.

docs: fix invalid syntax and wrong identifiers in code examples (#46694)

Kimaswa Emmanuel Yusufud35e8081d06c
diff --git a/apps/docs/content/guides/auth/auth-email-passwordless.mdx b/apps/docs/content/guides/auth/auth-email-passwordless.mdx
index 647211150ba..34e48a8b2b4 100644
--- a/apps/docs/content/guides/auth/auth-email-passwordless.mdx
+++ b/apps/docs/content/guides/auth/auth-email-passwordless.mdx
@@ -87,7 +87,7 @@ Read the [Deep Linking Documentation](/docs/guides/auth/native-mobile-deep-linki
```dart
Future<void> signInWithEmail() async {
- final AuthResponse res = await supabase.auth.signinwithotp(email: '[email protected]');
+ final AuthResponse res = await supabase.auth.signInWithOtp(email: '[email protected]');
}
```
diff --git a/apps/docs/content/guides/auth/third-party/firebase-auth.mdx b/apps/docs/content/guides/auth/third-party/firebase-auth.mdx
index b1e9f4380cf..fb9d28422b0 100644
--- a/apps/docs/content/guides/auth/third-party/firebase-auth.mdx
+++ b/apps/docs/content/guides/auth/third-party/firebase-auth.mdx
@@ -338,7 +338,7 @@ const { initializeApp } = require('firebase-admin/app');
const { getAuth } = require('firebase-admin/auth');
initializeApp();
-async function setRoleCustomClaim() => {
+async function setRoleCustomClaim() {
let nextPageToken = undefined
do {
diff --git a/apps/docs/content/guides/database/extensions/pg_graphql.mdx b/apps/docs/content/guides/database/extensions/pg_graphql.mdx
index 389dc09ddd6..ce5845773f0 100644
--- a/apps/docs/content/guides/database/extensions/pg_graphql.mdx
+++ b/apps/docs/content/guides/database/extensions/pg_graphql.mdx
@@ -90,7 +90,7 @@ returning the JSON
"edges": [
{
"node": {
- "id": 1
+ "id": 1,
"name": "My Blog"
}
}
diff --git a/apps/docs/content/guides/database/extensions/pgjwt.mdx b/apps/docs/content/guides/database/extensions/pgjwt.mdx
index fb0283e5dce..a77f55297df 100644
--- a/apps/docs/content/guides/database/extensions/pgjwt.mdx
+++ b/apps/docs/content/guides/database/extensions/pgjwt.mdx
@@ -55,8 +55,8 @@ It's good practice to create the extension within a separate schema (like `exten
## API
-- [`sign(payload json, secret text, algorithm text default 'HSA256')`](https://github.com/michelp/pgjwt#usage): Signs a JWT containing _payload_ with _secret_ using _algorithm_.
-- [`verify(token text, secret text, algorithm text default 'HSA256')`](https://github.com/michelp/pgjwt#usage): Decodes a JWT _token_ that was signed with _secret_ using _algorithm_.
+- [`sign(payload json, secret text, algorithm text default 'HS256')`](https://github.com/michelp/pgjwt#usage): Signs a JWT containing _payload_ with _secret_ using _algorithm_.
+- [`verify(token text, secret text, algorithm text default 'HS256')`](https://github.com/michelp/pgjwt#usage): Decodes a JWT _token_ that was signed with _secret_ using _algorithm_.
Where:
diff --git a/apps/docs/content/guides/deployment/branching/working-with-branches.mdx b/apps/docs/content/guides/deployment/branching/working-with-branches.mdx
index 15ef3b1c6bf..ecdceb08658 100644
--- a/apps/docs/content/guides/deployment/branching/working-with-branches.mdx
+++ b/apps/docs/content/guides/deployment/branching/working-with-branches.mdx
@@ -19,7 +19,7 @@ You can subscribe to webhook notifications when an action run completes on a per
"details_url": "https://supabase.com/dashboard/project/xuqpsshjxdecrwdyuxvs/branches",
"action_run": {
"id": "d5f8b4298d0a4d37b99e255c7837e7af",
- "created_at": "2025-10-17T02:27:10.133329324Z"
+ "created_at": "2025-10-17T02:27:10.133329324Z",
"steps": [
{
"name": "clone",
diff --git a/apps/docs/content/guides/integrations/supabase-for-platforms.mdx b/apps/docs/content/guides/integrations/supabase-for-platforms.mdx
index e1204f22222..c1ac2b31012 100644
--- a/apps/docs/content/guides/integrations/supabase-for-platforms.mdx
+++ b/apps/docs/content/guides/integrations/supabase-for-platforms.mdx
@@ -160,7 +160,7 @@ curl 'https://api.supabase.com/v1/projects/{ref}/branches' \
--data '{
"branch_name": "DEV",
"secrets": {
- "STRIPE_SECRET_KEY":"sk_test_123..."
+ "STRIPE_SECRET_KEY":"sk_test_123...",
"STRIPE_PUBLISHABLE_KEY":"pk_test_123..."
}
}'
diff --git a/apps/docs/content/guides/storage/management/copy-move-objects.mdx b/apps/docs/content/guides/storage/management/copy-move-objects.mdx
index 9103fdbed7d..844bdbf6d52 100644
--- a/apps/docs/content/guides/storage/management/copy-move-objects.mdx
+++ b/apps/docs/content/guides/storage/management/copy-move-objects.mdx
@@ -94,7 +94,7 @@ on storage.objects
for insert
to authenticated
with check (
- (storage.folder(name))[1] = (select auth.uid())
+ (storage.foldername(name))[1] = (select auth.uid())
);
create policy "User can update their own objects (in any buckets)"
diff --git a/apps/docs/content/troubleshooting/google-auth-fails-for-some-users-XcFXEu.mdx b/apps/docs/content/troubleshooting/google-auth-fails-for-some-users-XcFXEu.mdx
index b4deff01c56..c83f76463f9 100644
--- a/apps/docs/content/troubleshooting/google-auth-fails-for-some-users-XcFXEu.mdx
+++ b/apps/docs/content/troubleshooting/google-auth-fails-for-some-users-XcFXEu.mdx
@@ -42,9 +42,10 @@ It is happening because some Google Suite requires the explicit request of email
```js
const { data, error } = await supabase.auth.signInWithOAuth({
- provider: 'google'
+ provider: 'google',
options: {
- scopes: 'https://www.googleapis.com/auth/userinfo.email'
+ scopes: 'https://www.googleapis.com/auth/userinfo.email',
+ },
}
})
```
diff --git a/apps/docs/content/troubleshooting/how-to-interpret-and-explore-the-postgres-logs-OuCIOj.mdx b/apps/docs/content/troubleshooting/how-to-interpret-and-explore-the-postgres-logs-OuCIOj.mdx
index 3a0ac0ea1e1..d4711a6198c 100644
--- a/apps/docs/content/troubleshooting/how-to-interpret-and-explore-the-postgres-logs-OuCIOj.mdx
+++ b/apps/docs/content/troubleshooting/how-to-interpret-and-explore-the-postgres-logs-OuCIOj.mdx
@@ -136,7 +136,7 @@ When exploring the logs for atypical behavior, it's often strategic to filter ou
...query
where
-- Excluding routine events related to cron, PgBouncer, checkpoints, and successful connections
- not regexp_contains(event_message, '^cron|PgBouncer|checkpoint|connection received|authenticated|authorized';
+ not regexp_contains(event_message, '^cron|PgBouncer|checkpoint|connection received|authenticated|authorized');
```
### By timeframe
diff --git a/apps/docs/content/troubleshooting/increase-vector-lookup-speeds-by-applying-an-hsnw-index-ohLHUM.mdx b/apps/docs/content/troubleshooting/increase-vector-lookup-speeds-by-applying-an-hsnw-index-ohLHUM.mdx
index 0557d1b156a..6c5e0f6365b 100644
--- a/apps/docs/content/troubleshooting/increase-vector-lookup-speeds-by-applying-an-hsnw-index-ohLHUM.mdx
+++ b/apps/docs/content/troubleshooting/increase-vector-lookup-speeds-by-applying-an-hsnw-index-ohLHUM.mdx
@@ -58,7 +58,7 @@ If an address is returned, you should use your direct connection string found on
**3. Increase memory for index creation (optional)**
-The `maintance_work_mem` variable limits the maximum amount of memory that can be used by maintenance operations, such as vacuuming, altering, and indexing tables. In your session you should try to set it to a reasonably high value:
+The `maintenance_work_mem` variable limits the maximum amount of memory that can be used by maintenance operations, such as vacuuming, altering, and indexing tables. In your session you should try to set it to a reasonably high value:
```sql
set maintenance_work_mem to <several Gb's>; -- '#GB'
diff --git a/apps/docs/content/troubleshooting/pgcron-debugging-guide-n1KTaz.mdx b/apps/docs/content/troubleshooting/pgcron-debugging-guide-n1KTaz.mdx
index f6da4a213cf..7c027809550 100644
--- a/apps/docs/content/troubleshooting/pgcron-debugging-guide-n1KTaz.mdx
+++ b/apps/docs/content/troubleshooting/pgcron-debugging-guide-n1KTaz.mdx
@@ -58,7 +58,7 @@ If the query does not return a row, the worker has died. To revive it, you must
### Check the `cron.job_run_details` table for more information
-pg_cron creates logs in its own table `cron.job_run_details"`. The below query checks for issues from the past 5 days :
+pg_cron creates logs in its own table `cron.job_run_details`. The below query checks for issues from the past 5 days :
```sql
SELECT *
diff --git a/apps/docs/content/troubleshooting/rls-performance-and-best-practices-Z5Jjwv.mdx b/apps/docs/content/troubleshooting/rls-performance-and-best-practices-Z5Jjwv.mdx
index a2ef2eaa839..ec8820dff09 100644
--- a/apps/docs/content/troubleshooting/rls-performance-and-best-practices-Z5Jjwv.mdx
+++ b/apps/docs/content/troubleshooting/rls-performance-and-best-practices-Z5Jjwv.mdx
@@ -85,7 +85,7 @@ CREATE OR REPLACE FUNCTION has_role()
RETURNS boolean as
$$
begin
- return exists (select 1 from roles_table where auth.uid() = user_id and role = 'good_role')
+ return exists (select 1 from roles_table where auth.uid() = user_id and role = 'good_role');
end;
$$ language plpgsql security definer;
```
diff --git a/apps/docs/content/troubleshooting/supavisor-faq-YyP5tI.mdx b/apps/docs/content/troubleshooting/supavisor-faq-YyP5tI.mdx
index dbb15fb1d1b..981a0024565 100644
--- a/apps/docs/content/troubleshooting/supavisor-faq-YyP5tI.mdx
+++ b/apps/docs/content/troubleshooting/supavisor-faq-YyP5tI.mdx
@@ -103,7 +103,7 @@ CREATE DATABASE another_database;
Similarly, a database can have many database users, but most people just rely on the default user `postgres`.
```sql
-CREATE USER postgres WITH PASSWORD 'super-secret-password;
+CREATE USER postgres WITH PASSWORD 'super-secret-password';
CREATE USER some_new_user WITH PASSWORD 'password';
```