Skip to content

Improve docstrings #26

@Sporiff

Description

@Sporiff

My current approach to docstrings has been a bit haphazard, meaning some parts of the code are not currently adequately documented. In general, we need:

  1. Docstrings for each class
  2. Docstrings for each function (excluding overrides that don't change the function signature)
  3. Inline documentation where needed

Metadata

Metadata

Assignees

Labels

Type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions