Refactor to move scope management to ScopeManager class #265
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
sirbrillig
force-pushed
the
add/scope-manager
branch
from
765e508 to
3f68c53
Compare
sirbrillig
force-pushed
the
add/scope-manager
branch
from
6be0068 to
6a08465
Compare
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.
There are three ways that scope is tracked in the sniff:
scopeEndIndexCacheproperty.scopesproperty.scopeStartEndPairsproperty.Each of these properties was added to serve a different, but related, purpose. In this PR we modify the sniff to unify the three arrays and move them to a stand-alone class called
ScopeManager.