This repository has been archived by the owner on Mar 25, 2021. It is now read-only.
don't remove failure that starts at end of disabled range #3177
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
adidahiya
approved these changes
Aug 28, 2017
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
PR checklist
tslint:disable-next-linedisables two subsequent lines #3174Overview of change:
Don't remove failures that start at the end of a disabled range.
The bug caused line switches to disable failures that started at the beginning of the line following the disabled line.
Fixes: #3174
Is there anything you'd like reviewers to focus on?
CHANGELOG.md entry:
[bugfix] Fixed line switches to not disable failures in the next line following the disabled line