Description

url_launcher_platform_interface

Replace the current mechanism for protecting against implements with the common PlatformInterface class from the plugin_platform_interface package.

url_launcher

Update the unit test to work with the newly used PlatformInterface.
To keep CI green this includes a path dependency override.

This change is going to land and publish with the following sequence:

1. land this PR
2. publish url_launcher_platform_interface
3. land a PR to remove the dependency override from url_launcher, bump it's dependency on url_launcher_platform_interface, and re-enable the publish check for url_launcher
4. publish url_launcher

Related Issues

flutter/flutter#43368

Checklist

Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]). This will ensure a smooth and quick review process.

• I read the [Contributor Guide] and followed the process outlined there for submitting PRs.
• My PR includes unit or integration tests for all changed/updated/fixed behaviors (See [Contributor Guide]).
• All existing and new tests are passing.
• I updated/added relevant documentation (doc comments with ///).
• The analyzer (flutter analyze) does not report any problems on my PR.
• I read and followed the [Flutter Style Guide].
• The title of the PR starts with the name of the plugin surrounded by square brackets, e.g. [shared_preferences]
• I updated pubspec.yaml with an appropriate new version according to the [pub versioning philosophy].
• I updated CHANGELOG.md to add a description of the change.
• I signed the [CLA].
• I am willing to follow-up on review comments in a timely manner.

Breaking Change

Does your PR require plugin users to manually update their apps to accommodate your change?

• Yes, this is a breaking change (please indicate a breaking change in CHANGELOG.md and increment major revision).
• No, this is not a breaking change.

^ see changelog