-
Notifications
You must be signed in to change notification settings - Fork 1.5k
update messaging API based on the Firebase 7 #1056
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
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.
Changes LGTM. Paul brought up in a separate PR that there's an issue with merging these before Firebase 7 lands (doubly so in this case, since it updates a snippet on devsite). We need to resolve that issue before this PR can actually be merged.
yeah, i'm holding on this to see how they resolve the other PR. |
@morganchen12 @paulb777 Somehow this passes the check. Do you think this is still an issue? |
It's likely because the delegate is ObjC under the hood and ObjC protocols don't enforce types for method parameters, only selector matching. Seems strange that Swift wouldn't raise at least a warning though--maybe because |
Should this still be a blocker for submission? The other PR failed the CI, but this one not. |
I'm fine to merge if CI stays green and there is an eventual plan to update the quickstart. |
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.
Oh wait, the CI wasn't triggered by the swift cchange
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.
Right, it's only the firebase-ios-sdk change that is blocked. Sorry about my spinning.
No description provided.