-
Notifications
You must be signed in to change notification settings - Fork 889
Default to the stylish
formatter
#3460
Comments
I agree. Especially the missing rule name is quite annoying. |
Related: #2228 I think the output of Maybe we can make this configurable in tslint.json. Though I don't know what we would do when there are multiple config files involved. |
With what IDE? It's using the format |
How about adding that feature to the |
I'm talking about VSCode. Visual Studio also supports this.
I don't get how that would work when there are multiple lint errors in one file. The output of
|
The line/column is hidden in the title. So the output is actually:
You only get the first lint violation, but that's usually good enough, as the editor plugin takes over from there. |
This would be much easier to scan through the output. The current default output is a nightmare when you have quite a few errors. |
At the very least it would be nice to have an option in tslint.json that allows us to set which formatter we want to use by default. |
Now that the stylish formatter has clickable file names, let's adopt TypeScript's |
Removing the |
I think TSLint should have a nice out-of-the-box experience. The current default
prose
formatter is not very nice. It doesn't even show the rule name.ESLint, for example, defaults to their
stylish
formatter. So does XO.The text was updated successfully, but these errors were encountered: