Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve documentation #861

Open
DanRStevens opened this issue May 1, 2021 · 0 comments
Open

Improve documentation #861

DanRStevens opened this issue May 1, 2021 · 0 comments

Comments

@DanRStevens
Copy link
Collaborator

We should try to improve the API documentation. Currently we have a lot of "low value" comments, which I've sometimes taken to just removing as they only add clutter, without telling people anything new. Examples would be comments that simply restate what's already implied by a class or variable name.

In some cases, we should improve class or variable names so there is no need to document what they are for. Ideally a variable's use should be self evident from it's name, and so not require documentation.

For functions and classes, we should try to give examples of usage whenever possible. To some extent, the unit test code serves as example usage, though that's not an obvious place for people to look. Actually, I wonder if there might be a way for Doxygen to pick up certain blocks of unit test code and display it as part of the documentation. That might be a good way of having up-to-date documentation that is guaranteed to compile and function as expected. Since the unit tests are regularly run as part of CI, the code there should always be up-to-date.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant