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
I suppose it is necessary to implement - hide non-public methods, but can`t to decide how it must be done.
Why its important future - private methods is NOT a public interface and its clutter up documentation with unnecessary details.
For my code I use classical naming notation for 'private' methods - '_methodName' - name started by underscore.
May be add to CLI args something like --private-method group (by default) - group all non-public methods in one category, placed at the end of class docs --private-method fold group AND fold methods list, unfolding by click --private-method hide to wipe out from documentation all private methods
I may try to implement this behavior, so I looks for some help:
correct name for CLI key
correct name for CLI key options
is concept is ok?
PS.Sorry for 'broken English', not my mother tongue.
The text was updated successfully, but these errors were encountered:
Thanks for the suggestion! Sorry for the late reply. This is mostly handled by the --hide-private flag. If you want to implement the rest, feel free to submit a patch
I suppose it is necessary to implement - hide non-public methods, but can`t to decide how it must be done.
Why its important future - private methods is NOT a public interface and its clutter up documentation with unnecessary details.
For my code I use classical naming notation for 'private' methods - '_methodName' - name started by underscore.
May be add to CLI args something like
--private-method group
(by default) - group all non-public methods in one category, placed at the end of class docs--private-method fold
group AND fold methods list, unfolding by click--private-method hide
to wipe out from documentation all private methodsI may try to implement this behavior, so I looks for some help:
PS.Sorry for 'broken English', not my mother tongue.
The text was updated successfully, but these errors were encountered: