This repository has been archived by the owner on Jul 30, 2018. It is now read-only.
Move createHandle’s destroy from context to a flag #391
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.
Type: bug
The following has been addressed in the PR:
prettier
as per the readme code style guidelinesDescription:
If the destroy function in the response object from
createHandle
was called in a different context than the original,destroy
would be assigned to the call object and thedestructor
function would also be called in that context. By using a flag, we can guarantee the destructor is only called once regardless of associated context.