Add JSON docs back with tabs (#787)

Method:

vscode find and replace regex:
![Screenshot 2025-04-10 at 16 01
57@2x](https://github.com/user-attachments/assets/aba4685e-a1e1-4e28-9663-6308a06dc53d)

Copied and pasted from the red diffs:
https://github.com/xataio/pgroll/pull/773/files

AI'd updown.mdx

Check the preview link for a demo

Author: richardgill

docs/guides/updown.mdx

@@ -46,6 +46,7 @@ With the following records:
 We are adding a new check constraint to the table to make sure all first names are capitalized. We inspected our table and know
 that the check is on the application side. Thus, all data coming from it are valid.
 
+<YamlJsonTabs>
 ```yaml
 operations:
  - create_constraint:
@@ -60,6 +61,30 @@ operations:
     down:
      name: name
 ```
+```json
+{
+  "operations": [
+    {
+      "create_constraint": {
+        "name": "capitalized_name",
+        "table": "employee",
+        "type": "check",
+        "columns": [
+          "name"
+        ],
+        "check": "name = INITCAP(name)",
+        "up": {
+          "name": "name"
+        },
+        "down": {
+          "name": "name"
+        }
+      }
+    }
+  ]
+}
+```
+</YamlJsonTabs>
 
 Notice that both `up` and `down` migrations are set to `name` for `name` column. Thus, `pgroll` preserves the values in the column `name`.
 
@@ -79,6 +104,7 @@ In this example we are changing the type of a column from float to int.
 
 Each person's salary is stored in a float. We are converting the `salary` column from float to integer using `trunc`.
 
+<YamlJsonTabs>
 ```yaml
 operations:
  - alter_column:
@@ -88,6 +114,23 @@ operations:
     up: trunc(salary)
     down: salary
 ```
+```json
+{
+  "operations": [
+    {
+      "alter_column": {
+        "table": "employee",
+        "column": "salary",
+        "type": "integer",
+        "up": "trunc(salary)",
+        "down": "salary"
+      }
+    }
+  ]
+}
+
+```
+</YamlJsonTabs>
 
 After the migration, the `salary` column contains only integers.
 
@@ -103,6 +146,7 @@ After the migration, the `salary` column contains only integers.
 
 We are adding a new column that cannot be null named `location`. We are setting it to `New York` using the `up` expression.
 
+<YamlJsonTabs>
 ```yaml
 operations:
  - add_column:
@@ -113,6 +157,24 @@ operations:
        type: text
        nullable: false
 ```
+```json
+{
+  "operations": [
+    {
+      "add_column": {
+        "table": "employee",
+        "up": "'New York'",
+        "column": {
+          "name": "location",
+          "type": "text",
+          "nullable": false
+        }
+      }
+    }
+  ]
+}
+```
+</YamlJsonTabs>
 
 The table is backfilled:
 
@@ -128,6 +190,7 @@ The table is backfilled:
 
 We are adding a not null constraint to the `email` column. If the `email` column is not set, we are concatenating the column `nick` and `@company.com`.
 
+<YamlJsonTabs>
 ```yaml
 operations:
  - alter_column:
@@ -137,6 +200,22 @@ operations:
     up: SELECT CASE WHEN email IS NULL THEN nick || '@company.com' ELSE email END
     down: email
 ```
+```json
+{
+  "operations": [
+    {
+      "alter_column": {
+        "table": "employee",
+        "column": "email",
+        "nullable": false,
+        "up": "SELECT CASE WHEN email IS NULL THEN nick || '@company.com' ELSE email END",
+        "down": "email"
+      }
+    }
+  ]
+}
+```
+</YamlJsonTabs>
 
 After the migration is complete, everyone will have an email address:
 
@@ -177,6 +256,7 @@ Then we can call this function from the `up` migration:
 
 The complete migration is the following:
 
+<YamlJsonTabs>
 ```yaml
 operations:
  - create_constraint:
@@ -197,6 +277,30 @@ operations:
     down:
      bio: bio
 ```
+```json
+{
+  "operations": [
+    {
+      "create_constraint": {
+        "name": "limited_required_bio",
+        "table": "employee",
+        "type": "check",
+        "columns": [
+          "bio"
+        ],
+        "check": "length(bio) > 15 AND length(bio) < 100",
+        "up": {
+          "bio": "CASE WHEN bio IS NULL THEN 'this employee did not provide a bio' WHEN length(bio) <= 15 THEN bio || SELECT random_bio(16-length(bio)) WHEN length(bio) >= 100 THEN left(bio, 96) || '...' ELSE bio END"
+        },
+        "down": {
+          "bio": "bio"
+        }
+      }
+    }
+  ]
+}
+```
+</YamlJsonTabs>
 
 The `bio` column for `Alice` now contains extra 5 characters (`oivgd`) after the migration is complete:
 

docs/operations/add_column.mdx

@@ -5,6 +5,7 @@ description: An add column operation creates a new column on an existing table.
 
 ## Structure
 
+<YamlJsonTabs>
 ```yaml
 add_column:
   table: name of table to which the column should be added
@@ -26,6 +27,34 @@ add_column:
       column: name of referenced column
       on_delete: ON DELETE behaviour, can be CASCADE, SET NULL, RESTRICT, or NO ACTION. Default is NO ACTION
 ```
+```json
+{
+  "add_column": {
+    "table": "name of table to which the column should be added",
+    "up": "SQL expression",
+    "column": {
+      "name": "name of column",
+      "type": "postgres type",
+      "comment": "postgres comment for the column",
+      "nullable": true|false,
+      "unique": true|false,
+      "pk": true|false,
+      "default": "default value for the column",
+      "check": {
+        "name": "name of check constraint",
+        "constraint": "constraint expression"
+      },
+      "references": {
+        "name": "name of foreign key constraint",
+        "table": "name of referenced table",
+        "column": "name of referenced column",
+        "on_delete": "ON DELETE behaviour, can be CASCADE, SET NULL, RESTRICT, or NO ACTION. Default is NO ACTION",
+      }
+    }
+  }
+}
+```
+</YamlJsonTabs>
 
 The `up` SQL is used when a row is added to the old version of the table (ie, without the new column). In the new version of the table, the row's value for the new column is determined by the `up` SQL expression. The `up` SQL can be omitted if the new column is nullable or has a `DEFAULT` defined.
 

docs/operations/alter_column/add_check_constraint.mdx

@@ -5,6 +5,7 @@ description: An add check constraint operation adds a `CHECK` constraint to a co
 
 ## Structure
 
+<YamlJsonTabs>
 ```yaml
 alter_column:
   table: table name
@@ -15,14 +16,29 @@ alter_column:
   up: SQL expression
   down: SQL expression
 ```
+```json
+{
+  "alter_column": {
+    "table": "table name",
+    "column": "column name",
+    "check": {
+      "name": "check constraint name",
+      "constraint": "constraint expression"
+    },
+    "up": "SQL expression",
+    "down": "SQL expression"
+  }
+}
+```
+</YamlJsonTabs>
 
 The `up` SQL expression is used to migrate values from the column in the old schema version that aren't subject to the constraint to values in the new schema version that are subject to the constraint.
 
 ## Examples
 
 ### Add a `CHECK` constraint
 
-Add a `CHECK` constraint to the `title` column in the `posts` table. 
+Add a `CHECK` constraint to the `title` column in the `posts` table.
 
 The `up` SQL migrates values to ensure they meet the constraint. The `down` SQL copies values without modification from column in the new schema version to the column in the old schema version:
 

docs/operations/alter_column/add_foreign_key.mdx

@@ -5,6 +5,7 @@ description: Add a foreign key constraint to a column.
 
 ## Structure
 
+<YamlJsonTabs>
 ```yaml
 alter_column:
   table: table name
@@ -17,6 +18,23 @@ alter_column:
   up: SQL expression
   down: SQL expression
 ```
+```json
+{
+  "alter_column": {
+    "table": "table name",
+    "column": "column name",
+    "references": {
+      "name": "name of foreign key reference",
+      "table": "name of referenced table",
+      "column": "name of referenced column",
+      "on_delete": "ON DELETE behaviour, can be CASCADE, SET NULL, RESTRICT, or NO ACTION. Default is NO ACTION"
+    },
+    "up": "SQL expression",
+    "down": "SQL expression"
+  }
+}
+```
+</YamlJsonTabs>
 
 ## Examples
 

docs/operations/alter_column/add_not_null_constraint.mdx

@@ -5,6 +5,7 @@ description: Add not null operations add a `NOT NULL` constraint to a column.
 
 ## Structure
 
+<YamlJsonTabs>
 ```yaml
 alter_column:
   table: table name
@@ -13,6 +14,18 @@ alter_column:
   up: SQL expression
   down: SQL expression
 ```
+```json
+{
+  "alter_column": {
+    "table": "table name",
+    "column": "column name",
+    "nullable": false,
+    "up": "SQL expression",
+    "down": "SQL expression"
+  }
+}
+```
+</YamlJsonTabs>
 
 Use `up` to migrate values from the nullable column in the old schema view to the `NOT NULL` column in the new schema version. `down` is used to migrate values in the other direction.
 

docs/operations/alter_column/add_unique_constraint.mdx

@@ -5,6 +5,7 @@ description: Add unique operations add a `UNIQUE` constraint to a column.
 
 ## Structure
 
+<YamlJsonTabs>
 ```yaml
 alter_column:
   table: table name
@@ -14,6 +15,20 @@ alter_column:
   up: SQL expression
   down: SQL expression
 ```
+```json
+{
+  "alter_column": {
+    "table": "table name",
+    "column": "column name",
+    "unique": {
+      "name": "name of unique constraint"
+    },
+    "up": "SQL expression",
+    "down": "SQL expression"
+  }
+}
+```
+</YamlJsonTabs>
 
 Use the `up` SQL expression to migrate values from the old non-unique column in the old schema to the `UNIQUE` column in the new schema.
 

docs/operations/alter_column/change_comment.mdx

@@ -5,6 +5,7 @@ description: A change comment operation changes the comment on a column.
 
 ## Structure
 
+<YamlJsonTabs>
 ```yaml
 alter_column:
   table: table name
@@ -13,14 +14,26 @@ alter_column:
   up: SQL expression
   down: SQL expression
 ```
+```json
+{
+  "alter_column": {
+    "table": "table name",
+    "column": "column name",
+    "comment": "new comment for column" | null,
+    "up": "SQL expression",
+    "down": "SQL expression"
+  }
+}
+```
+</YamlJsonTabs>
 
 The comment is added directly to the column on migration start.
 
 ## Examples
 
 ### Alter many column properties
 
-An alter column migration performs many operations, including setting a comment: 
+An alter column migration performs many operations, including setting a comment:
 
 <ExampleSnippet example="35_alter_column_multiple.yaml" languange="yaml" />