This repository has been archived by the owner on Mar 25, 2021. It is now read-only.
Fix bug where the strict ts flag wasn't recognised correctly by no-unnecessary-type-assertion
#4841
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
JoshuaKGoldberg
suggested changes
Aug 31, 2019
JoshuaKGoldberg
approved these changes
Aug 31, 2019
This was referenced Nov 13, 2019
This was referenced Mar 18, 2020
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.
This commit fixes #4840
PR checklist
"strict": true#4840Overview of change:
Fixed simple bug.
Is there anything you'd like reviewers to focus on?
Nope.
CHANGELOG.md entry:
[bugfix] fix
no-unnecessary-type-assertionno error when"strict": truein compiler flags