-
Notifications
You must be signed in to change notification settings - Fork 492
How to disable tslint? #133
Comments
I think this is possible by creating an empty |
@foxylion Oh, Thanks.
I've been confused about it, because create-react-app said that
|
@bestwestern you're right, I've also removed all rules from So it seems the issue is back, how we should control tslint? |
Yeah It would be great disable tslint during development. App compilation would be faster without lint check. In my opinion ideal situation would be lint the code voluntarily when you want, not each recompilation. |
For example, in my case I've wanted to develop an electron app with the help of create-react-app-typescript, but I've needed to do some things that TSLint doesn't want me to do, like |
@1oginov I manged to disable tslint in my environment (react + typescript). In my case deleting all rules in |
Is there a way to disable it completely, while keeping config? |
Is there a way to make the linter wait until I'm done typing before yelling at me for semi colon errors? |
Why to waste time on linting on recompile when you can spare some cpu power on bitcoin mining? Has anyone figured out a way how to kill the linter completely? I'm just trying to check how costly is to migrate from plain jsx to ts and I honestly don't give a .... right now about linter. -.- |
Any updates on this? The internal linter is really wrecking our dev process. We run tslint in our IDEs and on commits / CI. Having a hidden lint config that we can't change is brutal. Any solutions? |
@gunn4r you can change your tslint according to your needs. Never had any issues with that. |
@maracuja-juice linter should not affect compilation. I want the app to work but I also want to see linter`s warnings. |
@dadayada, not necessarily. It really depends on your use case and how strict you want lint to be enforced. What I'm saying is that there's no single right or wrong way to use the linter - because different people use the same tool in different ways for different purposes. We can't cater to all of them with a single default. We can only decide on a reasonable one, which should serve most people. I'm in favor of a strict default and a well documented way to override it. |
To implement suggested workarounds in VS Code: |
My workaround is like the above, but reversed:
CI runs |
If you are using Webstorm, when you open the project the event log window says:
Supposedly clicking "Disable TSLint" allows deactivation. Not confirmed. |
It is unbelievable that there is no workaround for this provided by the tool authors. Many of us deal with existing projects where we didn’t have a way to choose the tooling and have to deal with what’s there. Please provide an official way to disable TSLint in development and have it only run within IDE. |
Now two tslint configs exist. One for development, one for production. In development, the defaultSeverity is set to "warning". Thus, compiling does not fail when breaking a rule. In production defaultSeverity is set to "error", resulting in failing compilation. When running `npm run build` tests run before building. Solution for config setup taken from wmonk/create-react-app-typescript#329 (comment) wmonk/create-react-app-typescript#133 (comment)
Now two tslint configs exist. One for development, one for production. In development, the defaultSeverity is set to "warning". Thus, compiling does not fail when breaking a rule. In production defaultSeverity is set to "error", resulting in failing compilation. When running `npm run build` tests run before building. Solution for config setup taken from wmonk/create-react-app-typescript#329 (comment) wmonk/create-react-app-typescript#133 (comment)
@gryzzly This is an open source project, and the authors don't get payed. There is no reason to point blame towards or demand from the authors. I am using this project just like you and was quite surprised to read your comment. |
@wmonk I do wonder if such a strict set of rules as default is the right way to go for such a package, which is used and presents itself as Typescript's "create-react-app". |
Description
Currently, tslint.json contains style-specific rules.
etc...
I've tried to use
react-scripts-ts
and I've feel frustrated to following lint errorExpected behavior
It is difficult that provide fundamental solution, I think.
Actual behavior
Report style error on
npm start
Related
The text was updated successfully, but these errors were encountered: