Update documentation about ws.send(...) return value #968
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
gwynne
approved these changes
Mar 29, 2024
gwynne
added
invalid code
9 tasks
|
i tried to push but it saying acces denied, i have the right remote. with ssh and http the same. |
|
problem is solved |
Merged
0xTim
pushed a commit
that referenced
this pull request
May 5, 2024
update cn doc for pr #968 Co-authored-by: redsun <[email protected]>
mattesmohr
added a commit
that referenced
this pull request
Jun 5, 2024
translation-update --------- Co-authored-by: Mattes Mohr <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
The current documentation incorrectly states that ws.send(...) returns a value which can be awaited. However, the WebSocket.send method does not have a return value.
Reference