Skip to content

API documentation gaps/errors #431

@renormalize

Description

@renormalize

What you would like to be added?

There are numerous places where Grove's API documentation has become inaccurate (with API evolution), or is not synced with the implementation behavior.

Why is this needed?

We need to fix the API documentation before becoming GA, to ensure there is no confusion within contributors, and consumers.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No fields configured for Task.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions