- 
 
- 
  Notifications
 You must be signed in to change notification settings 
- Fork 35
Add platform interface #34
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 platform interface #34
Conversation
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.
Can we put something more meaning full here (and following the Google Style guide)? Maybe something a long the lines of:
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.
The use of a default implementation is no longer recommended as it increases maintenance for something that most likely will never be used.
Current recommended solution is to make the _instance field nullable. Something like this:
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.
Adding a default implementation is no longer recommended, meaning this file should be deleted. See also comments in the google_api_availability_platform_interface.dart file.
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.
LGTM
✨ What kind of change does this PR introduce? (Bug fix, feature, docs update...)
This PR adds a platform interface for the plugin. This interface is part of the ongoing effort to refactor the code to use the federated plugin architecture. The
GooglePlayServicesAvailabilitymodel has been copied over, and its original version will be removed in a later PR.The plugin uses a non-federated architecture.
🆕 What is the new behavior (if this is a feature change)?
The plugin will function the same. The platform interface code is contained in the new directory
/google-api-availability-platform-interfaceand is not used outside of it.💥 Does this PR introduce a breaking change?
No.
🐛 Recommendations for testing
This PR adds tests for the newly added
GoogleApiAvailabilityPlatform. These tests can be found ingoogle-api-availability-platform-interface/test/google_api_availability_platform_interface_test.dart.📝 Links to relevant issues/docs
This PR is part of the ongoing effort to refactor this plugin to use the federated architecture requested in #33.
🤔 Checklist before submitting