Skip to content

Needs documentation #74

Description

@fortuna

If the library is to be reused by others, there should be robust documentation. Currently there's none. Even the Go documentation is bare. This also hurts delopers contributing to the project, including AI use.

Tip: you can use AI to help write documentation.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions