| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
|
I don't think this PR closes the linked issue. Also it states that these arguments are not documented but my read of each one does include documentation of what the variables are. They are not laid out in an Args: section but these are also nearly one line argument descriptions. This PR seems more pedantic than adding significant value. @BharatDeva can you expand a little on why you think the existing documentation is insufficient? |
Sorry, something went wrong.
There was a problem hiding this comment.
Looks good, thanks so much!
Sorry, something went wrong.
|
Ahh I didn't read the source issue, just that it sets out to do what it text here explains. |
Sorry, something went wrong.
|
@timsaucer these descriptions are very similar to what's found here https://datafusion.apache.org/user-guide/sql/scalar_functions.html#nvl |
Sorry, something went wrong.
|
Since the original reporter is happy with it, I'm merging |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Which issue does this PR close?
Related to #1463.
Rationale for this change
Some function docstrings in python/datafusion/functions.py include examples but do not describe their arguments. This makes the generated API docs harder to scan when users are looking up function signatures.
This PR makes a small, focused pass over the related null-handling helpers.
What changes are included in this PR?
Adds Args: sections for:
Are there any user-facing changes?
Yes, documentation-only. The generated API docs will include clearer argument descriptions for these functions. Runtime behavior is unchanged.
Validation
LLM-generated code disclosure
This documentation update was prepared with assistance from OpenAI Codex and manually reviewed before submission.