Skip to content

Update table tsconfig to use new compiler flags #471

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

Closed
wants to merge 2 commits into from

Conversation

michael-yx-wu
Copy link
Contributor

Let's use consistent compiler options across packages. Somewhat related: it also seems like tslint:latest has disabled the rules for these new flags to avoid being redundant.

@michael-yx-wu michael-yx-wu requested review from cmslewis and giladgray and removed request for giladgray January 12, 2017 22:40
@adidahiya
Copy link
Contributor

Instead of adding the same options in multiple places, can you use tsconfig.json inheritance with the "extends" keyword? https://www.typescriptlang.org/docs/handbook/tsconfig-json.html

We ought to have a tsconfig.base.json somewhere which defines a consistent set of compiler checks that we use across the packages. See #376

@michael-yx-wu
Copy link
Contributor Author

Looks like that's only available for Typescript 2.1.x. Should we track this and just duplicate the flags for now so that this doesn't block on #376?

@adidahiya
Copy link
Contributor

@michael-yx-wu yeah, that's fine; but I imagine bumping to 2.1 in this PR could be pretty simple too

@michael-yx-wu
Copy link
Contributor Author

michael-yx-wu commented Jan 13, 2017 via email

@giladgray
Copy link
Contributor

per ivogabe/gulp-typescript#459, this is not the correct approach.

@giladgray giladgray closed this Jan 18, 2017
@giladgray giladgray deleted the mw/table-tsconfig branch January 18, 2017 16:27
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.

3 participants