Use addEventListener
instead of onmessage
in WebWorkerPostMessageStream
#83
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
This pull request updates the
WebWorkerPostMessageStream
constructor to use theaddEventListener
method insteadof
onmessage
. The use ofaddEventListener
allows for proper handling of multiple event listeners and making theevent handling process more robust. It also ensures that the code is compatible with LavaMoat.
The
WebWorkerPostMessageStream
is used in our project for communication between web workers in our application. Thestream constructor uses
postMessage
andonmessage
to emit and receive messages, respectively. Theonmessage
method is used to handle incoming messages from multiple listeners. However, this method doesn't provide easy
management of event listeners. In this pull request, we change the constructor code to use
addEventListener
whichis more versatile and makes the code more maintainable.
This change will not have a significant impact on the performance of the application, but it makes the code more
readable and safer to maintain.
Changes
WebWorkerPostMessageStream
constructor to useaddEventListener
instead ofonmessage
.