-
Notifications
You must be signed in to change notification settings - Fork 12.8k
Apply more TSLint rules #3994
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
Comments
We also need a rule to capture having |
Do we have one for spaces between |
We also need one for the space after a method declaration but before the method body, ie disallowing: class A {
func(){
}
} and class A {
func(): void{
}
} |
Also a rule for enforcing inferred typing on primitive literal declarations, ie const member: string = "item" should be const member = "item" |
The rule added that will be added from this PR should also be enabled to disallow the |
@RyanCavanaugh |
A rule to forbid boolean parameters who aren't named. |
...also a no trailing whitespace rule. |
I tried to apply the no trailing whitespace rule locally but too many people are using editors where newline causes a smart indent that inserts whitespace. So then tslint flags tons of seemingly blank newlines as having trailing whitespace (because they're not simply a \n or \r\n). Would be nice to have on though. |
Including
namespace
instead ofmodule
(see Add no-internal-module rule palantir/tslint#517)else
/catch
/etc. on a different line (see Complement to [one-line]? palantir/tslint#88){
in interfaces, classes, enums, any sort of attached statement body, or type annotation.undefined
parameters who aren't named.null
Any other suggestions?
The text was updated successfully, but these errors were encountered: