chore: update Prettier to version 3.7.4 in doc scripts

Author: aaron-ang

ci/scripts/doc_prettier_check.sh

@@ -21,7 +21,7 @@ set -euo pipefail
 
 SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
 SCRIPT_NAME="$(basename "${BASH_SOURCE[0]}")"
-PRETTIER_VERSION="2.7.1"
+PRETTIER_VERSION="3.7.4"
 PRETTIER_TARGETS=(
   '{datafusion,datafusion-cli,datafusion-examples,dev,docs}/**/*.md'
   '!datafusion/CHANGELOG.md'

dev/update_config_docs.sh

@@ -239,6 +239,6 @@ EOF
 
 
 echo "Running prettier"
-npx prettier@2.3.2 --write "$TARGET_FILE"
+npx prettier@3.7.4 --write "$TARGET_FILE"
 
 echo "'$TARGET_FILE' successfully updated!"

dev/update_function_docs.sh

@@ -20,6 +20,7 @@
 
 set -e
 
+PRETTIER_VERSION="3.7.4"
 SOURCE_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
 cd "${SOURCE_DIR}/../" && pwd
 
@@ -114,7 +115,7 @@ echo "Running CLI and inserting aggregate function docs table"
 $PRINT_AGGREGATE_FUNCTION_DOCS_COMMAND >> "$TARGET_FILE"
 
 echo "Running prettier"
-npx prettier@2.3.2 --write "$TARGET_FILE"
+npx prettier@${PRETTIER_VERSION} --write "$TARGET_FILE"
 
 echo "'$TARGET_FILE' successfully updated!"
 
@@ -158,7 +159,7 @@ echo "Running CLI and inserting scalar function docs table"
 $PRINT_SCALAR_FUNCTION_DOCS_COMMAND >> "$TARGET_FILE"
 
 echo "Running prettier"
-npx prettier@2.3.2 --write "$TARGET_FILE"
+npx prettier@${PRETTIER_VERSION} --write "$TARGET_FILE"
 
 echo "'$TARGET_FILE' successfully updated!"
 
@@ -336,6 +337,6 @@ echo "Running CLI and inserting window function docs table"
 $PRINT_WINDOW_FUNCTION_DOCS_COMMAND >> "$TARGET_FILE"
 
 echo "Running prettier"
-npx prettier@2.3.2 --write "$TARGET_FILE"
+npx prettier@${PRETTIER_VERSION} --write "$TARGET_FILE"
 
 echo "'$TARGET_FILE' successfully updated!"

dev/update_metric_docs.sh

@@ -63,6 +63,6 @@ echo "Running CLI and inserting metric docs table"
 $PRINT_METRIC_DOCS_COMMAND >> "$TARGET_FILE"
 
 echo "Running prettier"
-npx prettier@2.3.2 --write "$TARGET_FILE"
+npx prettier@3.7.4 --write "$TARGET_FILE"
 
 echo "'$TARGET_FILE' successfully updated!"

docs/source/library-user-guide/query-optimizer.md

@@ -453,13 +453,11 @@ When analyzing expressions, DataFusion runs boundary analysis using interval ari
 Consider a simple predicate like age > 18 AND age <= 25. The analysis flows as follows:
 
 1. Context Initialization
-
    - Begin with known column statistics
    - Set up initial boundaries based on column constraints
    - Initialize the shared analysis context
 
 2. Expression Tree Walk
-
    - Analyze each node in the expression tree
    - Propagate boundary information upward
    - Allow child nodes to influence parent boundaries

docs/source/user-guide/concepts-readings-events.md

@@ -98,7 +98,6 @@ This is a list of DataFusion related blog posts, articles, and other resources.
 - **2024-10-16** [Blog: Candle Image Segmentation](https://www.letsql.com/posts/candle-image-segmentation/)
 
 - **2024-09-23 → 2024-12-02** [Talks: Carnegie Mellon University: Database Building Blocks Seminar Series - Fall 2024](https://db.cs.cmu.edu/seminar2024/)
-
   - **2024-11-12** [Video: Building InfluxDB 3.0 with the FDAP Stack: Apache Flight, DataFusion, Arrow and Parquet (Paul Dix)](https://www.youtube.com/watch?v=AGS4GNGDK_4)
 
   - **2024-11-04** [Video: Synnada: Towards “Unified” Compute Engines: Opportunities and Challenges (Mehmet Ozan Kabak)](https://www.youtube.com/watch?v=z38WY9uZtt4)

docs/source/user-guide/configs.md

@@ -2452,7 +2452,6 @@ date_bin(interval, expression, origin-timestamp)
 - **interval**: Bin interval.
 - **expression**: Time expression to operate on. Can be a constant, column, or function.
 - **origin-timestamp**: Optional. Starting point used to determine bin boundaries. If not specified defaults 1970-01-01T00:00:00Z (the UNIX epoch in UTC). The following intervals are supported:
-
   - nanoseconds
   - microseconds
   - milliseconds
@@ -2517,7 +2516,6 @@ date_part(part, expression)
 #### Arguments
 
 - **part**: Part of the date to return. The following date parts are supported:
-
   - year
   - isoyear (ISO 8601 week-numbering year)
   - quarter (emits value in inclusive range [1, 4] based on which quartile of the year the date is in)
@@ -2560,7 +2558,6 @@ date_trunc(precision, expression)
 - **precision**: Time precision to truncate to. The following precisions are supported:
 
   For Timestamp types:
-
   - year / YEAR
   - quarter / QUARTER
   - month / MONTH
@@ -2573,7 +2570,6 @@ date_trunc(precision, expression)
   - microsecond / MICROSECOND
 
   For Time types (hour, minute, second, millisecond, microsecond only):
-
   - hour / HOUR
   - minute / MINUTE
   - second / SECOND