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.
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
refactor(client): create Typescript MethodChannel on all platforms #2298
refactor(client): create Typescript MethodChannel on all platforms #2298
Changes from 12 commits
d5047ba
5c51517
4344ca8
b8be0f1
07c377d
42b26fc
ede86cc
11a8557
66250be
3febe62
e5bc49a
f270c65
e186372
a6b4c88
8b1e3cb
1f17917
f67e89c
c731ad2
e24fa09
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
[NOT THIS PR] I feel the name
pluginExecWithErrorCode
can be updated, instead of returning error codes, it throws aPlatformError
now.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.
Maybe the
await
(and theasync
above) is not needed here? IIRC,methodChannel.invoke
should already return aPromise<string>
.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 think it's clearer if we call await. Otherwise it reads as if we are returning a promise of a promise, even though Typescript auto-unwraps it.
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 would not recommend
return invoke(...)
in anasync function
. Instead, I would maybe preferreturn invoke(...)
in a regularfunction
, since we are not doing any multiple asynchronous steps here.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.
Done. But I also removed the switch to avoid mistakes. Previously I was implementing an interception there, and I needed the await.