fix(relations): remove some typevars in favor of Any #608
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
Remove the data type TypeVar in favor of Any. Then subclasses don't have to deal with this rule anymore. Ref typeddjango#168
Linkid
force-pushed
the
fix-relations-need-type-annotation
branch
from
e9fe7bd
to
3c65afa
Compare
|
Hello. I've forgotten some methods. This should be fixed in the latest commit. |
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.
I have made things!
RelatedFieldsubclasses can avoid dealing with data type and model typeTypeVars override, as they are not specific.This should fix the "Need type annotation for" that mypy raises for all related field subclasses.
Related issues
Ref #168