Skip to content
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

Closed
amirh opened this issue Jan 11, 2019 · 7 comments
Closed

Add template type parameter to invokeMethod calls in the plugins repo #26431

amirh opened this issue Jan 11, 2019 · 7 comments
Assignees
Labels
package flutter/packages repository. See also p: labels. team Infra upgrades, team productivity, code health, technical debt. See also team: labels.
Milestone

Comments

@amirh
Copy link
Contributor

amirh commented Jan 11, 2019

#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)

cc @jonahwilliams @Hixie

@amirh amirh added team Infra upgrades, team productivity, code health, technical debt. See also team: labels. plugin labels Jan 11, 2019
@amirh amirh added this to the Goals milestone Jan 11, 2019
amirh pushed a commit to amirh/plugins that referenced this issue Jan 11, 2019
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
amirh pushed a commit to amirh/plugins that referenced this issue Jan 11, 2019
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
amirh added a commit to flutter/plugins that referenced this issue Jan 12, 2019
…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
@Hixie
Copy link
Contributor

Hixie commented Jan 15, 2019

Next stable release should be February or March; shall we assign this to someone and put it in the April or May milestones?

@amirh amirh modified the milestones: Goals, April 2019 Jan 15, 2019
@amirh amirh self-assigned this Jan 15, 2019
@amirh
Copy link
Contributor Author

amirh commented Jan 15, 2019

done

andreidiaconu pushed a commit to andreidiaconu/plugins that referenced this issue Feb 17, 2019
…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
@amirh amirh modified the milestones: April 2019, May 2019 Mar 25, 2019
cyanglaz pushed a commit to flutter/plugins that referenced this issue Mar 29, 2019
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
cyanglaz pushed a commit to flutter/plugins that referenced this issue Mar 29, 2019
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
cyanglaz pushed a commit to flutter/plugins that referenced this issue Mar 29, 2019
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 was referenced May 31, 2019
@cyanglaz
Copy link
Contributor

cyanglaz commented Jun 4, 2019

This is completed, closing the issue.

@cyanglaz cyanglaz closed this as completed Jun 4, 2019
collinjackson pushed a commit to collinjackson/flutterfire-old2 that referenced this issue Jun 24, 2019
…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
collinjackson pushed a commit to collinjackson/flutterfire-old2 that referenced this issue Jun 24, 2019
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
collinjackson pushed a commit to firebase/flutterfire that referenced this issue Aug 14, 2019
…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
collinjackson pushed a commit to firebase/flutterfire that referenced this issue Aug 14, 2019
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
g123k pushed a commit to g123k/flutter_android_intent_with_parts that referenced this issue Sep 4, 2019
…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
ifananomali pushed a commit to ifananomali/camera that referenced this issue Sep 12, 2019
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
Akachu pushed a commit to Akachu/firebase_auth that referenced this issue Sep 16, 2019
…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
ryanheise pushed a commit to ryanheise/background_video_player that referenced this issue Sep 29, 2019
…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
nksteven pushed a commit to nksteven/ntf-firebase_messaging that referenced this issue Apr 8, 2020
…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
@github-actions
Copy link

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 flutter doctor -v and a minimal reproduction of the issue.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Aug 29, 2021
@flutter-triage-bot flutter-triage-bot bot added the package flutter/packages repository. See also p: labels. label Jul 5, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
package flutter/packages repository. See also p: labels. team Infra upgrades, team productivity, code health, technical debt. See also team: labels.
Projects
None yet
Development

No branches or pull requests

4 participants