This repository has been archived by the owner on Nov 16, 2023. It is now read-only.
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 disallows setting
"strict": false
in DefinitelyTyped packages, as there’s no package that hasstrict
set tofalse
, only 3 that have it set totrue
.I’m opening this as a new PR, because #275 depends on all DefinitelyTyped packages having
"noImplicitAny": true
, which will require fixing the remaining 49 packages that won’t yet be fixed by DefinitelyTyped/DefinitelyTyped#42682.I’ve also disallowed overriding
"strict": true
with"noImplicitAny"
,"noImplicitThis"
,"strictNullChecks"
or"strictFunctionTypes"
, as no DefinitelyTyped package does this either.