Ensure all private APIs are named as such

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Unresolved
    • Priority: Unknown
    • 5.0
    • Affects Version/s: None
    • Component/s: None
    • None
    • None
    • Python Drivers
    • None
    • None
    • None
    • None
    • None
    • None

      Context

      Many of our older APIs are not defined as private (named with a leading underscore) despite being unsupported for public use. This hurts refactoring and general maintainability: all methods should be clearly defined as public or private and named accordingly. We should decide which of these methods are actually public and rename the rest to reflect their private nature.

      Definition of done

      All private APIs should be prefixed with underscores.

      Pitfalls

      This may break some user workflows, hence the major release.

              Assignee:
              Unassigned
              Reporter:
              Noah Stapp
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: