Skip to content

Use brackets for module imports #487

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

Merged
merged 4 commits into from
Nov 22, 2017
Merged

Use brackets for module imports #487

merged 4 commits into from
Nov 22, 2017

Conversation

paulb777
Copy link
Member

No description provided.

@paulb777 paulb777 merged commit da93084 into master Nov 22, 2017
@paulb777 paulb777 deleted the pb-brackets branch November 22, 2017 17:19
@wilhuff
Copy link
Contributor

wilhuff commented Nov 22, 2017

So I don't mind this change, but want to understand the motivating principle behind it so that it can be applied more broadly.

Should brackets mean

  • system headers
  • that and external dependencies
  • that and anything specifically from outside the current pod

I don't understand why we would import FirebaseCore differently from e.g. GTMSessionFetcherLogging.h.

@paulb777
Copy link
Member Author

Yes, yes and yes.

I'm currently updating copybara for the changes from #444 and taking a step towards standardization and consistency and make the transformation rules simpler.

GTMSessionFetcher imports should used angled brackets. Most of them do and we should change the rest.

minafarid pushed a commit to minafarid/firebase-ios-sdk that referenced this pull request Jun 6, 2018
@firebase firebase locked and limited conversation to collaborators Nov 11, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants