jiayuasu opened a new pull request, #2680:
URL: https://github.com/apache/sedona/pull/2680

   ## Did you read the Contributor Guide?
   
   - Yes, I have read the [Contributor 
Rules](https://sedona.apache.org/latest/community/rule/) and [Contributor 
Development Guide](https://sedona.apache.org/latest/community/develop/)
   
   ## Is this PR related to a ticket?
   
   - Yes, and the PR name follows the format `[GH-XXX] my subject`. Closes #2679
   
   ## What changes were proposed in this PR?
   
   Add a `Return type:` field to every SQL function documentation page across 
all three platforms:
   
   - **Spark SQL** (`docs/api/sql/`): 243 geometry/geography function pages + 
95 raster function pages
   - **Flink** (`docs/api/flink/`): 221 function pages
   - **Snowflake** (`docs/api/snowflake/vector-data/`): 205 function pages
   
   Each individual function page now includes a `Return type:` line (e.g., 
`Return type: \`Geometry\``) between the `Format:` and `Since:` sections (or 
after `Format:` for Snowflake which has no `Since:` fieldEach individual 
funcded a **Return type** column to all summary tables:
   - `docs/api/sql/Geometry-Functions.md`
   - `docs/api/sql/Raster-Functions.md`
   - `docs/api/sql/geography/Geography-Functions.md`
   - `docs/api/flink/Geometry-Functions.md`
   - `docs/api/snowflake/vector-data/Geometry-Functions.md`
   
   Return types were determined by analyzing the Java/Scala source code for 
eachReturn types were determined by analyzing the Java/Scala source code for ea 
verReturn types were determined by analyzunctiReturn types were determined by 
analyzing the Java/Scala, accessors, editors, measurement, outputReturn types 
were determined by analyzing the Java/Scala source code for eachReturn tyting.
   - Verified summary tables render correctly with the new Return type column.
   - Confirmed no backslash-escaped angle brackets remain in summary tables 
(complex types like `Array<Geometry>` are wrapped in backtick code spans).
   
   ## Did this PR include necessary documentation updates?
   
   - Yes, I have updated the documentation. This PR is entirely a documentation 
update.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to