-
Notifications
You must be signed in to change notification settings - Fork 3.8k
[pigeon] Fix kotlin warning about calling bridge method #10632
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
Changes from 8 commits
c5a0497
8434383
e29d755
ded0ac9
3bde0ba
840ed28
5abaa3b
a8b0df1
5b75a9e
b171079
5e98a5b
c405fa3
b1e4279
0903bf6
cd16ddf
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -64,6 +64,8 @@ class EventListener : StreamEventsStreamHandler() { | |
| eventSink = sink | ||
| } | ||
|
|
||
| override fun onCancel(p0: Any?) {} | ||
|
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. @stuartmorgan-g @tarrinneal pigeon_example_app failed to build without this change. Does that mean this is a breaking change? If so, does that change what solution you prefer here?
Collaborator
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Sorry, looking again at the top-level interface class it has default implementations. I really thought it was just abstract declarations. So your previous version of the PR was the behavior-preserving one, and I was just confused. Sorry about that! |
||
|
|
||
| fun onIntEvent(event: Long) { | ||
| eventSink?.success(IntEvent(data = event)) | ||
| } | ||
|
|
||
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.
Is the "without implementing all of its methods" part right? The video_player code was implementing both of these methods.
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.
I am open to better wording but the class that implemented all the methods was an implementation of
*EventsStreamHandlernot the interface*PigeonEventChannelWrapper.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, I see. Since we don't expect Pigeon users to directly subclass the
Wrapperclass, let's just say "... warning when implementing an event stream handler."