Add use_modular_headers! to default Podfile#42204
Conversation
|
It looks like this pull request may not have tests. Please make sure to add tests before merging. If you need an exemption to this rule, contact Hixie. Reviewers: Read the Tree Hygiene page and make sure this patch meets those guidelines before LGTMing. |
Codecov Report
@@ Coverage Diff @@
## master #42204 +/- ##
==========================================
+ Coverage 59.93% 60.11% +0.18%
==========================================
Files 194 194
Lines 18877 18877
==========================================
+ Hits 11313 11348 +35
+ Misses 7564 7529 -35
Continue to review full report at Codecov.
|
|
Wow this is a nifty and helpful analyzer warning! Very few Generated files are actually checked in. 🤔 |
There was a problem hiding this comment.
Swift plugins should not need to add an Objective-C header if they don't need it.
ef9dd70 to
d525bd2
Compare
christopherfujino
left a comment
There was a problem hiding this comment.
weak LGTM, given I had to stack overflow search most of what was going on :)
d525bd2 to
893d28f
Compare
Description
use_modular_headers!to the default Podfile. Hopefully this lets Swift removeuse_frameworks!and build as libraries in the future (soon?). Compilation times will be faster because clang can use the module cache instead of doing pre-processing work. See http://blog.cocoapods.org/CocoaPods-1.5.0/ for how this works.NS_ASSUME_NONNULL_BEGINto get a compilation warning on a nilregistrysince the registration methods it calls require nonnull.#ifndef GeneratedPluginRegistrant_hin the same spot but I realized we couldn't because the template was using#includeinstead of#import. Migrate them over to avoid including headers multiple times.Related Issues
See #41007 for what supporting modules will unlock.
Tests
I updated the integration test Podfiles.
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