Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Always show protected members #1464

Closed
wants to merge 2 commits into from
Closed

Always show protected members #1464

wants to merge 2 commits into from

Conversation

SUPERCILEX
Copy link
Contributor

They are part of the public API and should always be shown.

Fixes #434

@BarkingBad
Copy link
Contributor

BarkingBad commented Sep 14, 2020

I think what we want here (according to #434) is to change binary option public vs includeNonPublic to possibility of specifying certain level of privacy of the API as it is in Javadoc. So there should be greater changes in configuration rather than assuming protected is public
obraz

@SUPERCILEX
Copy link
Contributor Author

Closing since I won't have time to fix the PR. Yup, I agree that you should be able to choose between different levels, but the default should still include protected members.

@SUPERCILEX SUPERCILEX closed this Sep 24, 2020
@mukeshsolanki
Copy link

Has this been resolved? as im facing issues with protected methods

@IgnatBeresnev
Copy link
Member

@mukeshsolanki it has, hopefully will be included in 1.6.20, see #434

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Allow including docs for internal/protected members but not private members
4 participants