-
Notifications
You must be signed in to change notification settings - Fork 885
Conversation
Can you add this rule to the README and |
Sure thing. |
Sorry this has taken so long to get reviewed. Can you please rebase these changes on the latest
|
|
||
private checkModifiers(node: ts.Node, current: IModifiers): void { | ||
if (!this.followsRules(current)) { | ||
var message = "Default access modifier on member/method not allowed"; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
change this to be a public static FAILURE_STRING
property on the Rule
class in this file -- similar to how other rule walkers are structured.
@meros I like this rule, and I want it in tslint :) Will you have time to address the PR comments soon? Or can I take the code and make a new PR? |
@adidahiya let's take this up when you get time and merge it in. also let's rename the rule to |
I think |
What would the value be? Just a Boolean? Sent from a phone On Jul 22, 2015, at 09:20, Adi Dahiya <notifications@github.commailto:notifications@github.com> wrote: I think member-access is slightly better — |
Hi guys, sorry I have been a little under the radar a while. I have been in vacation mode, and in sweden that is a non-negligible part of the year :) I will look into this again soon, probably next week. I see no problem in the comments so far. About the name, member-access doesn't really give a hint on what setting the flag would give. I like member-no-default-access the best, it's longer but the behaviour is spot on with what the module enforces. |
Please see this pull request instead: #552 |
Disallows public access modifiers that are not explicit in the class.