Add support for exclude in tsconfig.#637
Merged
basarat merged 1 commit intoTypeStrong:masterfrom Oct 4, 2015
Dashlane:feature/377-tsconfig-exclude
Merged
Add support for exclude in tsconfig.#637basarat merged 1 commit intoTypeStrong:masterfrom Dashlane:feature/377-tsconfig-exclude
basarat merged 1 commit intoTypeStrong:masterfrom
Dashlane:feature/377-tsconfig-exclude
Conversation
Please note that contrary to microsoft/TypeScript#3188, this support globs.
basarat
added a commit
that referenced
this pull request
Oct 4, 2015
Add support for exclude in tsconfig.
Member
Lets not document that it supports it :) Its an implementation detail...as long as it supports what is meant to be supported it is okay 🌹 |
This file contains hidden or 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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
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.
Aimed at closing #377. However, please note that contrary to microsoft/TypeScript#3188, this support globs. Also, this seems to be too simple... It does solve our usecase (excluding node_modules, same issue as #332).