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

Make various protected Node methods public #2544

Conversation

sphuber
Copy link
Contributor

@sphuber sphuber commented Feb 27, 2019

Fixes #2538

These methods are intended to be called from outside the class hierarchy
but were made protected (by prefixing them with an underscore) merely to
hide them from auto-completion and signal to users that they should not
be called by the user. However, this is the wrong usage of this feature
and methods that should be callable from the outside should not be
protected.

@sphuber sphuber force-pushed the fix_2538_wrongly_protected_methods branch 2 times, most recently from c63b67d to dcc2302 Compare February 27, 2019 16:00
These methods are intended to be called from outside the class hierarchy
but were made protected (by prefixing them with an underscore) merely to
hide them from auto-completion and signal to users that they should not
be called by the user. However, this is the wrong usage of this feature
and methods that should be callable from the outside should not be
protected.
@sphuber sphuber force-pushed the fix_2538_wrongly_protected_methods branch from dcc2302 to b66b98f Compare February 27, 2019 16:26
@coveralls
Copy link

Coverage Status

Coverage increased (+0.3%) to 70.054% when pulling b66b98f on sphuber:fix_2538_wrongly_protected_methods into acba3bd on aiidateam:provenance_redesign.

@sphuber sphuber deleted the fix_2538_wrongly_protected_methods branch February 28, 2019 08:11
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.

3 participants