Add linterOptions to tslint.json #1403
Conversation
- only enable type checking during tests when typeCheck: true is configured - fixes #1402
| @@ -24,6 +24,9 @@ import {arrayify, objectify, stripComments} from "./utils"; | |||
|
|
|||
| export interface IConfigurationFile { | |||
| extends?: string | string[]; | |||
| linterOptions?: { | |||
There was a problem hiding this comment.
Thinking we don't need this linterOptions property, typeCheck can reside at the top level.
Edit: We need to think carefully about the different classes of configuration options and whether or not they should be broken up or all provided at the same level. The current Linter constructor is sort of confusing already
|
I think if would be good to add support for this field when used via the CLI as well. It would only apply is the CLI used with the Sidenote: Should you be able to specify |
|
Changed my mind, the comments above weren't that important / not fully thought out yet. We'll need to think how we want to handle the |
|
For now, this is will remain a private/undocumented API as you mentioned until we have the end-user API figured out |
* Add linterOptions to tslint.json - only enable type checking during tests when typeCheck: true is configured - fixes palantir#1402 * Code style
typeCheck: trueis configuredI haven't documented this as a public API yet; we're only using it internally for tests. If we did want to make it public, we'd have to refactor tslint-cli.ts to read the configuration file before it tries to run the type checker on a program.