-
Notifications
You must be signed in to change notification settings - Fork 29.8k
Add missing pieces for 'driver' support on macOS #34376
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 missing pieces for 'driver' support on macOS #34376
Conversation
- Adds desktop projects to ApplicationPackageStore - Plumbs target overrides through the desktop builds
|
I've verified that this is enough to make flutter-driver work for macOS. I haven't tested Windows or Linux yet, but the corresponding pieces were obviously missing there as well so I added them at the same time. |
jonahwilliams
left a comment
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
| MacOSApp macOS; | ||
| WindowsApp windows; | ||
|
|
||
| Future<ApplicationPackage> getPackageForPlatform(TargetPlatform platform) async { |
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.
We could a simple smoke test here by asserting that the returned value for a particular platform is non-null
|
I ended up having to touch more files; |
|
In the interest of unblocking the macOS support, so that people can start using it on at least one platform, I've narrowed the scope of this to just macOS and removed the path.join change. I'll do a follow-up with Linux and Windows. |
- Adds desktop projects to ApplicationPackageStore - Plumbs target overrides through the macOS build
Description
Related Issues
None
Tests
I added the following tests: None
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.///).flutter analyze --flutter-repo) does not report any problems on my PR.Breaking Change
Does your PR require Flutter developers to manually update their apps to accommodate your change?