-
Notifications
You must be signed in to change notification settings - Fork 27.2k
-
Notifications
You must be signed in to change notification settings - Fork 27.2k
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
Add template type parameter to invokeMethod
calls in the plugins repo
#26431
Comments
flutter/flutter#26303 added a template argument to `invokeMethod`, which triggers the `strong_mode_implicit_dynamic_method` analyzer warning in many call sites in the plugins repo. We should add the type parameter to all these call sites, but we can only do that after bumping the Flutter dependency constraint which we will only do once the `invokeMethod` change makes it to the stable release. For now we're suppressing the warning in all call sites (we're not disabling the lint wholesale as we still want it for the rest of the code) See: flutter/flutter#26431
flutter/flutter#26303 added a template argument to `invokeMethod`, which triggers the `strong_mode_implicit_dynamic_method` analyzer warning in many call sites in the plugins repo. We should add the type parameter to all these call sites, but we can only do that after bumping the Flutter dependency constraint which we will only do once the `invokeMethod` change makes it to the stable release. For now we're suppressing the warning in all call sites (we're not disabling the lint wholesale as we still want it for the rest of the code) See: flutter/flutter#26431
…s. (#1065) flutter/flutter#26303 added a template argument to `invokeMethod`, which triggers the `strong_mode_implicit_dynamic_method` analyzer warning in many call sites in the plugins repo. We should add the type parameter to all these call sites, but we can only do that after bumping the Flutter dependency constraint which we will only do once the `invokeMethod` change makes it to the stable release. For now we're suppressing the warning in all call sites (we're not disabling the lint wholesale as we still want it for the rest of the code) See: flutter/flutter#26431
Next stable release should be February or March; shall we assign this to someone and put it in the April or May milestones? |
done |
…s. (flutter#1065) flutter/flutter#26303 added a template argument to `invokeMethod`, which triggers the `strong_mode_implicit_dynamic_method` analyzer warning in many call sites in the plugins repo. We should add the type parameter to all these call sites, but we can only do that after bumping the Flutter dependency constraint which we will only do once the `invokeMethod` change makes it to the stable release. For now we're suppressing the warning in all call sites (we're not disabling the lint wholesale as we still want it for the rest of the code) See: flutter/flutter#26431
Bump min flutter version to 1.2.0. Add template type parameter for invokeMethod calls. Updated invokeMethod and invokeMethod to using invokeListMethod and invokeMapMethod if any. flutter/flutter#26431
Bump min flutter version to 1.2.0. Add template type parameter for invokeMethod calls. Updated invokeMethod and invokeMethod to using invokeListMethod and invokeMapMethod if any. flutter/flutter#26431
Bump min flutter version to 1.2.0. Add template type parameter for invokeMethod calls. Updated invokeMethod and invokeMethod to using invokeListMethod and invokeMapMethod if any. flutter/flutter#26431
This is completed, closing the issue. |
…s. (#1065) flutter/flutter#26303 added a template argument to `invokeMethod`, which triggers the `strong_mode_implicit_dynamic_method` analyzer warning in many call sites in the plugins repo. We should add the type parameter to all these call sites, but we can only do that after bumping the Flutter dependency constraint which we will only do once the `invokeMethod` change makes it to the stable release. For now we're suppressing the warning in all call sites (we're not disabling the lint wholesale as we still want it for the rest of the code) See: flutter/flutter#26431
Bump min flutter version to 1.2.0. Add template type parameter for invokeMethod calls. Updated invokeMethod and invokeMethod to using invokeListMethod and invokeMapMethod if any. flutter/flutter#26431
…s. (#1065) flutter/flutter#26303 added a template argument to `invokeMethod`, which triggers the `strong_mode_implicit_dynamic_method` analyzer warning in many call sites in the plugins repo. We should add the type parameter to all these call sites, but we can only do that after bumping the Flutter dependency constraint which we will only do once the `invokeMethod` change makes it to the stable release. For now we're suppressing the warning in all call sites (we're not disabling the lint wholesale as we still want it for the rest of the code) See: flutter/flutter#26431
Bump min flutter version to 1.2.0. Add template type parameter for invokeMethod calls. Updated invokeMethod and invokeMethod to using invokeListMethod and invokeMapMethod if any. flutter/flutter#26431
…s. (#1065) flutter/flutter#26303 added a template argument to `invokeMethod`, which triggers the `strong_mode_implicit_dynamic_method` analyzer warning in many call sites in the plugins repo. We should add the type parameter to all these call sites, but we can only do that after bumping the Flutter dependency constraint which we will only do once the `invokeMethod` change makes it to the stable release. For now we're suppressing the warning in all call sites (we're not disabling the lint wholesale as we still want it for the rest of the code) See: flutter/flutter#26431
Bump min flutter version to 1.2.0. Add template type parameter for invokeMethod calls. Updated invokeMethod and invokeMethod to using invokeListMethod and invokeMapMethod if any. flutter/flutter#26431
…s. (firebase#1065) flutter/flutter#26303 added a template argument to `invokeMethod`, which triggers the `strong_mode_implicit_dynamic_method` analyzer warning in many call sites in the plugins repo. We should add the type parameter to all these call sites, but we can only do that after bumping the Flutter dependency constraint which we will only do once the `invokeMethod` change makes it to the stable release. For now we're suppressing the warning in all call sites (we're not disabling the lint wholesale as we still want it for the rest of the code) See: flutter/flutter#26431
…s. (#1065) flutter/flutter#26303 added a template argument to `invokeMethod`, which triggers the `strong_mode_implicit_dynamic_method` analyzer warning in many call sites in the plugins repo. We should add the type parameter to all these call sites, but we can only do that after bumping the Flutter dependency constraint which we will only do once the `invokeMethod` change makes it to the stable release. For now we're suppressing the warning in all call sites (we're not disabling the lint wholesale as we still want it for the rest of the code) See: flutter/flutter#26431
…s. (#1065) flutter/flutter#26303 added a template argument to `invokeMethod`, which triggers the `strong_mode_implicit_dynamic_method` analyzer warning in many call sites in the plugins repo. We should add the type parameter to all these call sites, but we can only do that after bumping the Flutter dependency constraint which we will only do once the `invokeMethod` change makes it to the stable release. For now we're suppressing the warning in all call sites (we're not disabling the lint wholesale as we still want it for the rest of the code) See: flutter/flutter#26431
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of |
#26303 added a template argument to
invokeMethod
, which triggers thestrong_mode_implicit_dynamic_method
analyzer warning in many call sites in the plugins repo.We should add the type parameter to all these call sites, but we can only do that after bumping the Flutter dependency constraint which we will only do once the
invokeMethod
change makes it to the stable release.For now we're suppressing the warning in all call sites (we're not disabling the lint wholesale as we still want it for the rest of the code)
cc @jonahwilliams @Hixie
The text was updated successfully, but these errors were encountered: