TypeScript - implicit or explicit access modifiers?

[DanielSchaffer]

Using implicit public access modifiers seems to be the de-facto standard for Angular - members are assumed to be public unless otherwise specified:

@Component({ ... })
export class SomeComponent {

  // public constructor
  constructor() {
    ...
  }

  // public method
  ngOnInit(): void {
    ...
  }

  private helperMethod(): string {
    ...
  }

}

However, the tslint "recommended" settings require explicit member access for everything (except constructors, I think?)

@Component({ ... })
export class SomeComponent {

  // public constructor
  constructor() {
    ...
  }

  public ngOnInit(): void {
    ...
  }

  private helperMethod(): string {
    ...
  }

}

The rationale for tslint's setting is:

Explicit visibility declarations can make code more readable and accessible for those new to TS.

Other languages such as C# default to private, unlike TypeScript’s default of public. Members lacking a visibility declaration may be an indication of an accidental leak of class internals.

Is the above a risk for SE developers? What are our preferences?

[shanejann]

I lean towards always showing the public keyword (again, with the exception of the constructor). My argument here is that other languages have different implicit visibilities. My one example of this is Java, where the methods are considered package-visible (I'll admit my Java is rusty, so I don't know how true this is).

In scenarios like this, any dev knows exactly how visible a function or member is. Sure, it's tedious to write out the whole word, but if you ask me, it's always better to be explicit about stuff.