docs: Prefer literal over folded strings in YAML

Author: igorlukanin

docs/pages/product/apis-integrations/recipes/cast-numerics.mdx

@@ -16,7 +16,7 @@ numeric measure:
 ```yaml
 cubes:
   - name: cube_with_big_numbers
-    sql: >
+    sql: |
       SELECT              123::BIGINT AS number UNION ALL
       SELECT 9007199254740991::BIGINT AS number UNION ALL
       SELECT 9999999999999999::BIGINT AS number

docs/pages/product/apis-integrations/recipes/sorting.mdx

@@ -29,7 +29,7 @@ Consider the following data model:
 ```yaml
 cubes:
   - name: sort_nulls
-    sql: >
+    sql: |
       SELECT 1234 AS value UNION ALL
       SELECT 5678 AS value UNION ALL
       SELECT NULL AS value

docs/pages/product/caching/recipes/incrementally-building-pre-aggregations-for-a-date-range.mdx

@@ -21,7 +21,7 @@ Let's use an example of a cube with a nested SQL query:
 ```yaml
 cubes:
   - name: users_with_organizations
-    sql: >
+    sql: |
       WITH users AS (
         SELECT
           md5(company) AS organization_id,
@@ -168,7 +168,7 @@ properties][ref-schema-ref-preagg-buildrange]:
 ```yaml
 cubes:
   - name: users_with_organizations
-    sql: >
+    sql: |
       WITH users AS (
         SELECT
           md5(company) AS organization_id,

docs/pages/product/caching/recipes/refreshing-select-partitions.mdx

@@ -125,7 +125,7 @@ cubes:
         granularity: day
         partition_granularity: month # this is where we specify the partition
         refreshKey:
-          sql: >
+          sql: |
             SELECT max(updated_at) FROM public.orders WHERE
             {FILTER_PARAMS.orders.created_at.filter('created_at')}
 ```

docs/pages/product/configuration/recipes/custom-data-model-per-tenant.mdx

@@ -394,7 +394,7 @@ This is the `products` cube for the `avocado` tenant:
 ```yaml
 cubes:
   - name: products
-    sql: >
+    sql: |
       SELECT * FROM public.Products WHERE MOD (id, 2) = 1
 ```
 
@@ -417,7 +417,7 @@ This is the `products` cube for the `mango` tenant:
 ```yaml
 cubes:
   - name: products
-    sql: >
+    sql: |
       SELECT * FROM public.Products WHERE MOD (id, 2) = 0
 ```
 

docs/pages/product/configuration/reference/config.mdx

@@ -1089,7 +1089,7 @@ You can use the custom value from extend context in your data model like this:
 
 cubes:
   - name: users
-    sql: >
+    sql: |
       SELECT *
       FROM users
       WHERE organization_id={{ securityContext['active_organization'] }}

docs/pages/product/data-modeling/concepts.mdx

@@ -85,7 +85,7 @@ cube(`orders`, {
 ```yaml
 cubes:
   - name: orders
-    sql: >
+    sql: |
       SELECT *
       FROM orders, line_items
       WHERE orders.id = line_items.order_id
@@ -567,7 +567,7 @@ Consider the following cube:
 ```yaml
 cubes:
   - name: employees
-    sql: >
+    sql: |
       SELECT 1 AS id, 'Ali' AS first_name, 20 AS age, 'Los Gatos' AS city UNION ALL
       SELECT 2 AS id, 'Bob' AS first_name, 30 AS age, 'San Diego' AS city UNION ALL
       SELECT 3 AS id, 'Eve' AS first_name, 40 AS age, 'San Diego' AS city

docs/pages/product/data-modeling/concepts/calculated-members.mdx

@@ -29,7 +29,7 @@ integer value.
 ```yaml
 cubes:
   - name: orders
-    sql: >
+    sql: |
       SELECT 1 AS id, 'processing' AS status UNION ALL
       SELECT 2 AS id, 'completed'  AS status UNION ALL
       SELECT 3 AS id, 'completed'  AS status
@@ -322,7 +322,7 @@ between `orders` and `users`:
 ```yaml
 cubes:
   - name: orders
-    sql: >
+    sql: |
       SELECT 1 AS id, 1 AS user_id UNION ALL
       SELECT 2 AS id, 1 AS user_id UNION ALL
       SELECT 3 AS id, 2 AS user_id
@@ -347,7 +347,7 @@ cubes:
         relationship: one_to_many
 
   - name: users
-    sql: >
+    sql: |
       SELECT 1 AS id, 'Alice' AS name UNION ALL
       SELECT 2 AS id, 'Bob'   AS name
 
@@ -453,7 +453,7 @@ granularity. It can be one of the [default granularities][ref-default-granularit
 ```yaml
 cubes:
   - name: users
-    sql: >
+    sql: |
       SELECT '2025-01-01T00:00:00Z' AS created_at UNION ALL
       SELECT '2025-02-01T00:00:00Z' AS created_at UNION ALL
       SELECT '2025-03-01T00:00:00Z' AS created_at
@@ -561,7 +561,7 @@ relationship between `orders` and `users`:
 ```yaml
 cubes:
   - name: orders
-    sql: >
+    sql: |
       SELECT 1 AS id, 1 AS user_id UNION ALL
       SELECT 2 AS id, 1 AS user_id UNION ALL
       SELECT 3 AS id, 2 AS user_id
@@ -582,7 +582,7 @@ cubes:
         relationship: one_to_many
 
   - name: users
-    sql: >
+    sql: |
       SELECT 1 AS id, 'Alice' AS name UNION ALL
       SELECT 2 AS id, 'Bob'   AS name
 

docs/pages/product/data-modeling/concepts/code-reusability-extending-cubes.mdx

@@ -141,7 +141,7 @@ First, the `sql` parameter can be overridden in each child cube:
 ```yaml
 cubes:
   - name: product_purchases
-    sql: >
+    sql: |
       SELECT *
       FROM events
       WHERE {FILTER_PARAMS.product_purchases.timestamp.filter('time')}
@@ -172,7 +172,7 @@ in the SQL query:
 ```yaml
 cubes:
   - name: base_events
-    sql: >
+    sql: |
       SELECT *
       FROM events
       WHERE

docs/pages/product/data-modeling/concepts/data-blending.mdx

@@ -191,7 +191,7 @@ cube(`all_sales`, {
 ```yaml
 cubes:
   - name: all_sales
-    sql: >
+    sql: |
       SELECT
         amount,
         user_id AS customer_id,
@@ -228,7 +228,7 @@ cubes:
           - sql: "{CUBE}.row_type = 'retail'"
 
       - name: online_revenue_percentage
-        sql: >
+        sql: |
           {online_revenue} /
           NULLIF({online_revenue} + {offline_revenue}, 0)
         type: number