Better API documentation #4438
Labels
docs needed
Issues that require documentation
good first issue
Issues with this label are great for first time contributors
What problem does this feature solve?
Much of the API documentation doesn't do much to explain what a given component is and how it would normally be used. Writing a few sentences about what each component is, and how/when you'd use it, could help people understand the library quite a bit better.
For example:
What does the proposed API look like?
n/a
The text was updated successfully, but these errors were encountered: