Detect bad plugins and work around them#18093
Merged
Merged
Conversation
Contributor
|
@RyanCavanaugh can you update the PR |
RyanCavanaugh
force-pushed
the
detectBadPlugins
branch
from
September 8, 2017 00:10
e6e9bff to
67f2716
Compare
Member
Author
|
Pushed the wrong commit into this one; fixed |
mhegazy
approved these changes
Sep 11, 2017
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.
3 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.
The Angular LS plugin isn't providing a correct full proxy. I expect they won't be the last to do this, so this PR detects the situation and works around it.