Fixes #3334: Add support for custom parameter classes in mypy plugin #3335
+36
−29
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
dlstadther
reviewed
Jan 18, 2025
| @@ -109,6 +109,7 @@ def _task_parameter_field_callback(self, ctx: FunctionContext) -> Type: | |||
| # if no `default` argument is found, return AnyType with unannotated type. | |||
| except ValueError: | |||
| return AnyType(TypeOfAny.unannotated) | |||
| print(ctx.context) | |||
There was a problem hiding this comment.
Let's remove print() statements before merging.
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.
Description
Fix for custom parameter classes in mypy plugin.
Motivation and Context
I'm using custom parameter classes in my code, and I'd like to benefit from the new mypy plugin. The change is not the prettiest one but the smallest I've found.
Have you tested this? If so, how?
I've updated unittests.