-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Separate Core private versus internal headers #5759
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
Conversation
Generated by 🚫 Danger |
| #import "FirebaseCore/Tests/Unit/FIRTestCase.h" | ||
|
|
||
| #import <FirebaseCore/FIRAnalyticsConfiguration.h> | ||
| #import "FirebaseCore/Sources/FIRAnalyticsConfiguration.h" |
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.
May be a silly question but just to confirm for here and other tests - is it alright that we're not using framework imports in test code?
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.
Yes. The tests are in the repo and using repo-relative imports should allow Swift Package Manager to build them without change. We should leave framework import testing for integration tests.
Fix the reorganization part of #3777.
Based on testing in #5758, move Core headers only used by Core from "Private" to "Sources".