Add motion functions to api docs #4057
Merged
+30
−6
Conversation
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
zm711
added
documentation
chrishalcrow
approved these changes
Jul 12, 2025
Member
chrishalcrow
left a comment
chrishalcrow
left a comment
There was a problem hiding this comment.
New docstrings! More API!
alejoe91
approved these changes
Jul 14, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
Fixes #3083.
The second half of missing api functions. Now added to the api.rst.
Also a tiny fix. The semantic (that Chris and I discussed) for saying backward compatible would be to save that it is for versions greater than what we are being compatible to. So I think we want to actually list this compatibility as > 100 rather than < 101. Otherwise I think we would rewrite that whole statement.