[codex] clarify UDF signature annotations#907
Open
therealclvn wants to merge 1 commit into
Open
Conversation
soxofaan
reviewed
Jul 17, 2026
|
|
||
| ### Fixed | ||
|
|
||
| - Clarify UDF documentation on required function type annotations. ([#757](https://github.com/Open-EO/openeo-python-client/issues/757)) |
Member
There was a problem hiding this comment.
The changelog has changed in the meantime, this entry has to be moved
soxofaan
marked this pull request as ready for review
July 17, 2026 11:36
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.
Closes #757.
What changed
apply_datacubeexample so users can translate the rendered Sphinx signature back to Python code.Validation
git diff --checkast.parse.Note: I did not run a full Sphinx docs build because Sphinx is not installed in the available local Python environments.