Search Terms
private in:title
Problem
A class field declared as private via typescript access modifier is still overridable by subclasses (including external downstream ones), so one may want to document it to announce its existence and warn that it should not be overridden. A javascript #private class field doesn't share this problem, so excluding it from documentation entirely can still make sense.
Suggested Solution
An excludePrivateClassFields or similarly-named option that defaults to the value of excludePrivate, or excludePrivate additionally accepting something like a #privateOnly value
Related
Search Terms
private in:titleProblem
A class field declared as
privatevia typescript access modifier is still overridable by subclasses (including external downstream ones), so one may want to document it to announce its existence and warn that it should not be overridden. A javascript#privateclass field doesn't share this problem, so excluding it from documentation entirely can still make sense.Suggested Solution
An
excludePrivateClassFieldsor similarly-named option that defaults to the value ofexcludePrivate, orexcludePrivateadditionally accepting something like a#privateOnlyvalueRelated