Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

(clean): remove redundant tsconfig strict opts in templates #673

Conversation

agilgur5
Copy link
Collaborator

@agilgur5 agilgur5 commented Apr 12, 2020

  • noImplicitAny, noImplicitThis, alwaysStrict, strictNullChecks,
    strictFunctionTypes, and strictPropertyInitialization are already
    enabled by strict, no need to configure them twice
    • beginners could also be confused by redundant options (like I was
      at one point)
      • and including them may have also unintentionally encouraged folks
        to turn them off

Fixes #619 . Similar to removals in #475 but for the external tsconfig templates, instead of just the internal one

See also my related microsoft/TypeScript-Website#500 that I made when double-checking config options

- noImplicitAny, noImplicitThis, alwaysStrict, strictNullChecks,
  strictFunctionTypes, and strictPropertyInitialization are already
  enabled by strict, no need to configure them twice
  - beginners could also be confused by redundant options (like I was
    at one point)
    - and including them may have also unintentionally encouraged folks
      to turn them off
@agilgur5 agilgur5 merged commit 2dd4396 into jaredpalmer:master Apr 12, 2020
Copy link
Collaborator Author

@agilgur5 agilgur5 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍 Same removals in all 3 files, only redundant options were removed.

paul-vd pushed a commit to EezyQuote/tsdx that referenced this pull request Dec 1, 2020
…mer#673)

- noImplicitAny, noImplicitThis, alwaysStrict, strictNullChecks,
  strictFunctionTypes, and strictPropertyInitialization are already
  enabled by strict, no need to configure them twice
  - beginners could also be confused by redundant options (like I was
    at one point)
    - and including them may have also unintentionally encouraged folks
      to turn them off
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Redundant compiler options in template tsconfigs
1 participant