remove static typings from Returns in docstrings #236
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
This stack of pull requests is managed by Graphite. Learn more about stacking. Join @CunliangGeng and the rest of your teammates on |
CunliangGeng
force-pushed
the
update_docstrings_format
branch
from
d4763c2
to
8ca6993
Compare
gcroci2
approved these changes
Mar 28, 2024
CunliangGeng
force-pushed
the
update_docstrings_format
branch
from
8ca6993
to
e84971a
Compare
Merge activity
|
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.
Remove static typings from Returns in docstrings. mkdocs will automatically extract typings for Returns (see https://mkdocstrings.github.io/griffe/docstrings/#google-section-returns), so we won't bother writing that in the docstrings.