getFormattingScanner: Ensure scanner is closed, and avoid global variables#18293
Merged
1 commit merged intoSep 7, 2017
Merged
getFormattingScanner: Ensure scanner is closed, and avoid global variables#182931 commit merged into
1 commit merged into
Conversation
mhegazy
approved these changes
Sep 6, 2017
This pull request was closed.
This file contains hidden or 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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
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.
.close()the formatting scanner; just use a callback and close when the callback is over. (Ensuring that resources are reclaimed may help with avoiding global-state bugs like ingulp runtests --test gefails #10683.)scannervariable, which is entirely unnecessary as it's only used locally to one function.