This repository has been archived by the owner on Sep 30, 2024. It is now read-only.
fix: implement notifier on deno side #797
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
MarcosSpessatto
approved these changes
Sep 5, 2024
d-gubert
approved these changes
Sep 9, 2024
Merged
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
What? ⛵
Implement the notifier on the Deno side to be able to return a function to stop the
notify.typingaccessor.Why? 🤔
The
modify.getNotifier().typing()returns a function to stop thetypingnotification. It's not possible to serialize the function when communicating apps.engine and Deno, so it's necessary to implement the notify accessor on the Deno side.Links 🌎
PS 👀
SUP-650