Add docstring examples for Scalar regex, crypto, struct and other#1422
Open
ntjohnson1 wants to merge 2 commits intoapache:mainfrom
Open
Add docstring examples for Scalar regex, crypto, struct and other#1422ntjohnson1 wants to merge 2 commits intoapache:mainfrom
ntjohnson1 wants to merge 2 commits intoapache:mainfrom
Conversation
…ctions Add example usage to docstrings for Scalar regex, crypto, struct and other functions to improve documentation. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
kosiew
reviewed
Mar 13, 2026
Contributor
kosiew
left a comment
kosiew
left a comment
There was a problem hiding this comment.
@ntjohnson1
thanks for your contribution
|
|
||
| Searches ``values`` for the ``n``-th occurrence of ``regex``, starting at position | ||
| ``start`` (the first position is 1). Returns the starting or ending position based | ||
| on ``end_position``. Use ``flags`` to control regex behavior and ``sub_expr`` to |
Contributor
There was a problem hiding this comment.
end_position is not in the function signature
Comment on lines
1120
to
+1121
| def sha224(arg: Expr) -> Expr: | ||
| """Computes the SHA-224 hash of a binary string.""" | ||
| """Computes the SHA-224 hash of a binary string. |
Contributor
There was a problem hiding this comment.
These four examples (sha224 through sha512) are almost identical and only assert len(...) > 0. Could we simplify this by showing one representative hash example with a concrete expected value, then cross-reference the sibling helpers or digest()?
That would reduce doc drift and make the examples more informative.
| ... dfn.col("a"), dfn.col("b") | ||
| ... ).alias("s") | ||
| ... ) | ||
| >>> result.collect_column("s")[0].as_py() == {"c0": 1, "c1": 2} |
Contributor
There was a problem hiding this comment.
Could this example call out why the keys are c0 and c1?
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Which issue does this PR close?
Rationale for this change
Add example usage to docstrings for Scalar regex, crypto, struct and other functions to improve documentation.
What changes are included in this PR?
The first PR was basically adding a docstring to everything in functions. I broke it apart into a PR (that already merged) for the infra. I then reviewed and merged an example PR of adding the docstrings in parts. This is now the follow up opening a handful of PRs for the remaining functions in functions.py Everything is co-authored with Claude since I used claude to extend the handwritten examples I wrote for reference and to split apart the large PR rather than doing it manually.
I've reviewed all the code prior to PR.
Are there any user-facing changes?
No