-
Notifications
You must be signed in to change notification settings - Fork 29.7k
Add an ephemeral directory to Windows projects #40194
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 an ephemeral directory to Windows projects #40194
Conversation
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
Codecov Report
@@ Coverage Diff @@
## master #40194 +/- ##
=========================================
+ Coverage 58.11% 58.72% +0.6%
=========================================
Files 192 192
Lines 18443 18444 +1
=========================================
+ Hits 10719 10831 +112
+ Misses 7724 7613 -111
Continue to review full report at Codecov.
|
Updates the Windows builds for the breaking change in flutter/flutter#40194 Note: plugins continue to hard-code the cache dir instead of using FLUTTER_EPHEMERAL_DIR since currently they share the generated properties file, but need a project-local copy of the cache. That whole structure needs to be reworked, so the fact that it's currently hard-coded isn't worth trying to fix right now (e.g., by making FLUTTER_EPHEMERAL_DIR relative).
Moves files generated in windows/flutter/ as part of the build to an ephemeral/ subdirectory, matching the approach used on macOS (and in the future, Windows). Adds that directory to the generated properties file to minimize hard-coding of paths in the project.
Description
Moves files generated in windows/flutter/ as part of the build to an ephemeral/ subdirectory, matching the approach used on macOS (and in the future, Windows).
Adds that directory to the generated properties file to minimize hard-coding of paths in the project.
Tests
I added the following tests: None. Updated existing tests.
Replace this with a list of the tests that you added as part of this PR. A change in behaviour with no test covering it
will likely get reverted accidentally sooner or later. PRs must include tests for all changed/updated/fixed behaviors. See Test Coverage.
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?
This is a breaking change for Windows, which is explicitly not stable.