Skip to content

Document and enforce public vs private API #69

Description

@MatthewPeterKelly

All functions and classes in the library are currently part of the public API, although many are intended to be for internal use only. We should decide what will be part of the public API (for focus on thorough documentation) and what should be part of the private API (easier to clean-up the code without worrying about breaking things with every change to a private function).

  1. Decide what will be in the public API
  2. Decide how to separate the private and public sections of the code
  3. Implement!

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions