Change deprecated setMockMethodCallHandler to TestDefaultBinaryMessengerBinding.instance.defaultBinaryMessenger.setMockMethodCallHandler

[natsuk4ze]

Changed deprecated setMockMethodCallHandler in experimental\federated_plugin\federated_plugin

to fix error : 'setMockMethodCallHandler' is deprecated and shouldn't be used. Use tester.binding.defaultBinaryMessenger.setMockMethodCallHandler or TestDefaultBinaryMessengerBinding.instance.defaultBinaryMessenger.setMockMethodCallHandler instead. Pass the channel as the first argument. This feature was deprecated after v3.9.0-19.0.pre. Try replacing the use of the deprecated member with the replacement. - deprecated_member_use in PR #1740

Pre-launch Checklist

• I read the [Flutter Style Guide] recently, and have followed its advice.
• I signed the [CLA].
• I read the [Contributors Guide].
• I updated/added relevant documentation (doc comments with ///).
• All existing and new tests are passing.

[domesticmouse]

LGTM, assuming tests pass

[natsuk4ze]

I'm going to go modify the code a bit.

[domesticmouse]

I'm going to go modify the code a bit.

Is this change only for beta and master?

[natsuk4ze]

Is this change only for beta and master?

I'm a newbie so I'm not sure what your question means 😢I'm working on a branch forked from the master branch. I'm trying to fix a few things that didn't pass tests.

[natsuk4ze]

I guess it means that the test is failing only in flutter beta and master. Either way I have made a few changes and need to see how this test goes.

[domesticmouse]

Is this change only for beta and master?

I'm a newbie so I'm not sure what your question means 😢I'm working on a branch forked from the master branch. I'm trying to fix a few things that didn't pass tests.

I think you'll have a saner time if you try developing a fix on beta branch. I suspect master is starting to take on breaking changes that won't surface in the next stable release, which is what I'm aiming at stabilising on for this repository.

[natsuk4ze]

@domesticmouse I will close this and the #1740 PR once and start over with a new branch from the beta branch. Is that OK?
And are there fewer test failures in the beta branch?

[domesticmouse]

@domesticmouse I will close this and the #1740 PR once and start over with a new branch from the beta branch. Is that OK? And are there fewer test failures in the beta branch?

The beta branch is going to be landed when Flutter 3.10 goes stable. It's WIP until then.

I'll create a new PR with the changes required to fix federated_plugin.