Skip to content

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

fix: Fix torubleshooting frontmatter validation (#47220)

Jeremias Menichelli21785b2418c3
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
index 09c1c7314bf..27d6f72b96a 100644
--- 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
@@ -6,7 +6,6 @@ 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)).
diff --git a/apps/docs/features/docs/Troubleshooting.utils.common.mjs b/apps/docs/features/docs/Troubleshooting.utils.common.mjs
index c938dced206..de3e1028e48 100644
--- a/apps/docs/features/docs/Troubleshooting.utils.common.mjs
+++ b/apps/docs/features/docs/Troubleshooting.utils.common.mjs
@@ -61,6 +61,7 @@ export const TroubleshootingSchema = z
z.enum([
'ai',
'ai-tools',
+ 'api',
'auth',
'branching',
'cli',
@@ -129,12 +130,10 @@ export async function getAllTroubleshootingEntriesInternal() {
const parseResult = validateTroubleshootingMetadata(frontmatter)
if ('error' in parseResult) {
- console.error(
- `Error validating troubleshooting metadata\nEntry:%O\nError:%O`,
- frontmatter,
- parseResult.error
+ throw Error(
+ `Error validating troubleshooting metadata for ${filePath}`,
+ { cause: parseResult.error }
)
- return null
}
const mdxTree = fromMarkdown(content, {