-
-
Notifications
You must be signed in to change notification settings - Fork 264
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. Weβll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Decouple FunctionDef
and Lambda
#2115
Decouple FunctionDef
and Lambda
#2115
Conversation
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## main #2115 +/- ##
==========================================
- Coverage 92.74% 92.73% -0.02%
==========================================
Files 94 94
Lines 10981 11007 +26
==========================================
+ Hits 10184 10207 +23
- Misses 797 800 +3
Flags with carried forward coverage won't be shown. Click here to find out more.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
π
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's do the breaking change, but let's cover the new code if reasonable.
""" | ||
if "method" in self.type: | ||
return "Method" | ||
return "Function" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should be trivial to cover (?)
Type of Changes
Description
As discussed in #2112 we really need to decouple this nodes. I think this warrants a 3.0 release for the next release. We don't need to do any of the other deprecations but this is just 100% necessary for
Mypy
but will also 100% break code of users.Let me know what you think!
/CC @nickdrozd