WorryFree Computers   »   [go: up one dir, main page]

Skip to content
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

Stop using CocoaPods private headers #6572

Merged
merged 7 commits into from
Oct 2, 2020
Merged

Stop using CocoaPods private headers #6572

merged 7 commits into from
Oct 2, 2020

Conversation

paulb777
Copy link
Member
@paulb777 paulb777 commented Sep 25, 2020

Stop using CocoaPods private headers to be more consistent with Swift Package Manager.

Instead internal API's between repo pods should be referenced with repo-relative imports.

FirebaseCore Private's are kept for now because of internal non-Firebase client usage via CocoaPods (Flutter for example)

@google-cla google-cla bot added cla: no and removed cla: yes labels Oct 1, 2020
@paulb777 paulb777 changed the base branch from firebase7-main to master October 2, 2020 00:09
@paulb777 paulb777 added cla: yes and removed cla: no labels Oct 2, 2020
@firebase firebase deleted a comment from google-cla bot Oct 2, 2020
@paulb777 paulb777 marked this pull request as ready for review October 2, 2020 00:14
Copy link
Member
@ryanwilson ryanwilson left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Discussed offline, but we should keep Core's private headers to avoid breaking any downstream dependencies like Flutter and RN depending on it.

@paulb777 paulb777 merged commit 12c9e3f into master Oct 2, 2020
@paulb777 paulb777 deleted the pb-rm-cp-private branch October 2, 2020 16:11
@firebase firebase locked and limited conversation to collaborators Nov 2, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants