(clean): remove redundant tsconfig strict opts in tests #690
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
- removed them in the templates in a previous commit, forgot to remove
them in the tests too
- presets would really help with this duplication / inconsistency
problem
- noImplicitAny, noImplicitThis, alwaysStrict, strictNullChecks,
strictFunctionTypes, and strictPropertyInitialization are already
enabled by strict, no need to configure them twice
agilgur5
commented
Apr 20, 2020
paul-vd
pushed a commit
to EezyQuote/tsdx
that referenced
this pull request
Dec 1, 2020
) - removed them in the templates in a previous commit, forgot to remove them in the tests too - presets would really help with this duplication / inconsistency problem - noImplicitAny, noImplicitThis, alwaysStrict, strictNullChecks, strictFunctionTypes, and strictPropertyInitialization are already enabled by strict, no need to configure them twice
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.
removed them in the templates in a previous commit, forgot to remove
them in the tests too
problem
noImplicitAny, noImplicitThis, alwaysStrict, strictNullChecks,
strictFunctionTypes, and strictPropertyInitialization are already
enabled by strict, no need to configure them twice
Follow-up to #673 . Another reason for #634