Added a possibility to remove webview handlers #52
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
onRequest()andonNotification()now returnDisposableinstead ofMessenger- This change removes method chaining but provides consistent disposal patternonRequest<P, R>(type: RequestType<P, R>, handler: RequestHandler<P, R>): DisposableonNotification<P>(type: NotificationType<P>, handler: NotificationHandler<P>): Disposablemessenger.onRequest(type, handler).start()with separate calls:messenger.onRequest(type, handler); messenger.start();onRequestDisposable()andonNotificationDisposable()methods - These are no longer needed sinceonRequest()andonNotification()now return disposables directlyNew Features
unregisterHandler(method: string): boolean- Programmatically unregister message handlers by method nametrueif handler was successfully removed,falseif no handler existedSee #51