Documentation edits made through Mintlify web editor

Author: mintlify[bot]

usage/sync-rules/parameter-queries.mdx

@@ -8,7 +8,7 @@ Parameter queries allow parameters to be defined on a bucket to group data. Thes
 bucket_definitions:
   # Bucket Name
   user_buckets:
-    # Paramter Query
+    # Parameter Query
     parameters: SELECT request.user_id() as user_id
     # Data Query
     data:
@@ -47,47 +47,45 @@ request.jwt() ->> 'app_metadata.custom_field' -- custom field added by a service
   A previous syntax for parameter queries used `token_parameters`. Expand the below for details on how to migrate to the recommended syntax above.
 </Note>
 
-<Accordion
-  title="Previous Syntax"
->
-The previous syntax for parameter queries used `token_parameters.user_id` to return the JWT subject. Example:
+<Accordion title="Previous Syntax">
+  The previous syntax for parameter queries used `token_parameters.user_id` to return the JWT subject. Example:
 
-```yaml
-bucket_definitions:
-  by_user_parameter:
-    parameters: SELECT token_parameters.user_id as user_id
-    data:
-      - SELECT * FROM lists WHERE lists.owner_id = bucket.user_id
-```
-### Migrate to Recommended Syntax
+  ```yaml
+  bucket_definitions:
+    by_user_parameter:
+      parameters: SELECT token_parameters.user_id as user_id
+      data:
+        - SELECT * FROM lists WHERE lists.owner_id = bucket.user_id
+  ```
 
-The new functions available in sync rules are:
+  ### Migrate to Recommended Syntax
 
-1. `request.jwt()`: Returns the entire (signed) JWT payload as a JSON string.
-2. `request.parameters()`: Returns [client parameters](/usage/sync-rules/advanced-topics/client-parameters) as a JSON string.
-3. `request.user_id()`: Returns the token subject, same as `request.jwt() ->> 'sub'` and also the same as `token_parameters.user_id` in the previous syntax.
+  The new functions available in sync rules are:
 
-The major difference from the previous `token_parameters` is that all payloads are preserved as-is, which can make usage a little more intuitive. This also includes JWT payload fields that were not previously accessible.
+  1. `request.jwt()`: Returns the entire (signed) JWT payload as a JSON string.
+  2. `request.parameters()`: Returns [client parameters](/usage/sync-rules/advanced-topics/client-parameters) as a JSON string.
+  3. `request.user_id()`: Returns the token subject, same as `request.jwt() ->> 'sub'` and also the same as `token_parameters.user_id` in the previous syntax.
 
-Migrating to the new syntax:
+  The major difference from the previous `token_parameters` is that all payloads are preserved as-is, which can make usage a little more intuitive. This also includes JWT payload fields that were not previously accessible.
 
-1. `token_parameters.user_id` references can simply be updated to `request.user_id()`
-2. Custom parameters can be updated from `token_parameters.my_custom_field` to `request.jwt() ->> 'parameters.my_custom_field'`
-   1. This example applies if you keep your existing custom JWT as is.
-   2. Supabase users can now make use of [Supabase's standard JWT structure](https://supabase.com/docs/guides/auth/jwts#jwts-in-supabase) and reference `app_metadata.my_custom_field` directly.
+  Migrating to the new syntax:
 
-Example:
+  1. `token_parameters.user_id` references can simply be updated to `request.user_id()`
+  2. Custom parameters can be updated from `token_parameters.my_custom_field` to `request.jwt() ->> 'parameters.my_custom_field'`
+     1. This example applies if you keep your existing custom JWT as is.
+     2. Supabase users can now make use of [Supabase's standard JWT structure](https://supabase.com/docs/guides/auth/jwts#jwts-in-supabase) and reference `app_metadata.my_custom_field` directly.
 
-```yaml
-bucket_definitions:
-  by_user_parameter:
-    # request.user_id() is the same as the previous token_parameter.user_id
-    parameters: SELECT request.user_id() as user_id
-    data:
-      - SELECT * FROM lists WHERE lists.owner_id = bucket.user_id
-```
-</Accordion>
+  Example:
 
+  ```yaml
+  bucket_definitions:
+    by_user_parameter:
+      # request.user_id() is the same as the previous token_parameter.user_id
+      parameters: SELECT request.user_id() as user_id
+      data:
+        - SELECT * FROM lists WHERE lists.owner_id = bucket.user_id
+  ```
+</Accordion>
 
 #### Filter on additional columns
 
@@ -132,7 +130,7 @@ bucket_definitions:
 
 In this example, a single query can return multiple sets of bucket parameters for a single user.
 
-Keep in mind that the total number of buckets per user should remain limited (< 1,000), so don't make buckets too granular.
+Keep in mind that the total number of buckets per user should remain limited (\< 1,000), so don't make buckets too granular.
 
 ```yaml
 bucket_definitions:
@@ -181,7 +179,7 @@ bucket_definitions:
       - SELECT * FROM todos WHERE todos.list_id = bucket.list_id
 ```
 
-Keep in mind that the total number of buckets per user should remain limited (< 1,000), so don't make buckets too granular.
+Keep in mind that the total number of buckets per user should remain limited (\< 1,000), so don't make buckets too granular.
 
 #### Global buckets
 
@@ -214,4 +212,4 @@ Notable features and restrictions:
 1. Only simple `SELECT` statements are supported.
 2. No `JOIN`, `GROUP BY` or other aggregation, `ORDER BY`, `LIMIT`, or subqueries are supported.
 3. For token parameters, only `=` operators are supported, and `IN` to a limited extent.
-4. A limited set of operators and functions are supported — see [Operators and Functions](/usage/sync-rules/operators-and-functions).
+4. A limited set of operators and functions are supported — see [Operators and Functions](/usage/sync-rules/operators-and-functions).