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

chore(lint, ios): fix xcode warnings wherever possible #6061

Merged
merged 12 commits into from
Feb 9, 2022

Conversation

mikehardy
Copy link
Collaborator

Description

Our iOS build was getting pretty noisy, this quiets it down. Still one that we could potentially get rid of but the rest are from upstream in firebase-ios-sdk

Related issues

Release Summary

conventional commits -> rebase merge

Checklist

  • I read the Contributor Guide and followed the process outlined there for submitting PRs.
    • Yes
  • My change supports the following platforms;
    • Android
    • iOS
  • My change includes tests;
    • e2e tests added or updated in packages/\*\*/e2e
    • jest tests added or updated in packages/\*\*/__tests__
  • I have updated TypeScript types that are affected by my change.
  • This is a breaking change;
    • Yes
    • No

Test Plan

Compile should pass with very few compile warnings, all e2e should pass


Think react-native-firebase is great? Please consider supporting the project with any of the below:

@vercel
Copy link

vercel bot commented Feb 9, 2022

This pull request is being automatically deployed with Vercel (learn more).
To see the status of your deployments, click below or on the icon next to each commit.

react-native-firebase – ./

🔍 Inspect: https://vercel.com/invertase/react-native-firebase/2Tm3LpBPvv9YBCEc4Dy5WvGrkDkk
✅ Preview: https://react-native-firebase-git-mikehardy-xcode-warnings-invertase.vercel.app

react-native-firebase-next – ./website_modular

🔍 Inspect: https://vercel.com/invertase/react-native-firebase-next/E3HqYT8wVn1CCYDsYEW35zWRgAtp
✅ Preview: Canceled

[Deployment for 57d59d7 canceled]

@mikehardy mikehardy added the Workflow: Pending Merge Waiting on CI or similar label Feb 9, 2022
@mikehardy mikehardy force-pushed the @mikehardy/xcode-warnings branch from d60cd20 to 374a59a Compare February 9, 2022 21:53
@mikehardy mikehardy changed the title lint(ios): fix xcode warnings wherever possible chore(lint, ios): fix xcode warnings wherever possible Feb 9, 2022
@vercel vercel bot temporarily deployed to Preview – react-native-firebase-next February 9, 2022 21:54 Inactive
@mikehardy mikehardy force-pushed the @mikehardy/xcode-warnings branch from 374a59a to 43482c5 Compare February 9, 2022 22:00
@vercel vercel bot temporarily deployed to Preview – react-native-firebase-next February 9, 2022 22:00 Inactive
@mikehardy mikehardy force-pushed the @mikehardy/xcode-warnings branch from 43482c5 to 57d59d7 Compare February 9, 2022 22:03
@codecov
Copy link

codecov bot commented Feb 9, 2022

Codecov Report

Merging #6061 (68912e4) into main (211b753) will decrease coverage by 0.05%.
The diff coverage is 95.00%.

❗ Current head 68912e4 differs from pull request most recent head 57d59d7. Consider uploading reports for the commit 57d59d7 to get more accurate results

@@             Coverage Diff              @@
##               main    #6061      +/-   ##
============================================
- Coverage     53.01%   52.96%   -0.04%     
+ Complexity      628      622       -6     
============================================
  Files           208      208              
  Lines         10205    10214       +9     
  Branches       1623     1626       +3     
============================================
  Hits           5409     5409              
- Misses         4545     4551       +6     
- Partials        251      254       +3     

@mikehardy
Copy link
Collaborator Author

a continuation / completion of #5935 really - after they were really visible it was easy to tamp things down all the way

@mikehardy
Copy link
Collaborator Author

Chasing upstream warnings here firebase/firebase-ios-sdk#9331

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant