Skip to content

More documentation needed #360

@autarch

Description

@autarch

I'm trying to read through the v1 example scheduler but it's very difficult to follow. It calls a lot of APIs that are barely documented. Even when a func is documented it's usually just a very minimal description of what it does.

What's missing is any context. I have no idea why any of these calls are important, nor do I have any clue of how this all fits together.

What I'd like to see is much more detailed documentation that explains both what a func does and why I would use it, along with references to how it fits in with other parts of the API.

Now I'm sure patches are welcome but I'm really not in a position to offer one. I don't see how anyone could do this without extremely intimate knowledge of the code base.

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