You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 25, 2021. It is now read-only.
Many people coming from C# and friends assume class members to be private by default. That's not true in TypeScript. A rule that requires all constructs have an explicit privacy modifier would help a lot.
Auto-fixing logic should be easy: just add "public ".
The text was updated successfully, but these errors were encountered:
Retargeting for just auto-fixing... would you consider it valid to auto-fix to public? It would be nice to auto-detect the ability to be private or protected, but that would be a dangerous change and hard with exported constructs.
JoshuaKGoldberg
changed the title
Rule for explicit privacies
--fix for explicit privacies in member-access
Jun 29, 2017
TypeScript code being linted
Many people coming from C# and friends assume class members to be
private
by default. That's not true in TypeScript.A rule that requires all constructs have an explicit privacy modifier would help a lot.Auto-fixing logic should be easy: just add "
public
".The text was updated successfully, but these errors were encountered: