Skip to content

Better documentation #24

@gabrielodom

Description

@gabrielodom

Despite the volume of documented functions, the documentation itself is Don't RY in places where we need repetition and Do RY in places we don't. I need a fresh pair of eyes to look at this package documentation and tell me what places don't have the right documentation, and what places have superfluous or extraneous documentation.

Metadata

Metadata

Assignees

Labels

documentationImprovements or additions to documentation

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions