docs: clarify Member.current_timeout expiry
#1063
Merged
Conversation
This file contains 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
shiftinv
added
t: documentation
Victorsitou
approved these changes
Jun 22, 2023
shiftinv
added a commit
that referenced
this pull request
Oct 30, 2023
Tiny documentation change to clarify that `Member.current_timeout` also returns `None` when the current timeout value is in the past, allowing users to safely rely on this behavior.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
Tiny documentation change to clarify that
Member.current_timeoutalso returnsNonewhen the current timeout value is in the past, allowing users to safely rely on this behavior.Checklist
pdm lintpdm pyright