-
Notifications
You must be signed in to change notification settings - Fork 132
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
Added Doxygen documentation for all files #28
Conversation
Codecov Report
@@ Coverage Diff @@
## master #28 +/- ##
=====================================
Coverage 100% 100%
=====================================
Files 13 13
Lines 536 536
=====================================
Hits 536 536
Continue to review full report at Codecov.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@FloatingFowl Thanks for adding Doxygen documentation! I think that only the Doxyfile should be committed, as the rest of the documentation files can be generated right before they're published after a successful CI build as you suggested.
Deleted /docs/html and Updated .gitignore Added documentation for all files
@faheel The doc files have been removed |
I'm quite busy currently so I'll only be able to review the updated documentation in detail by the end of next week (May 11). |
6bf4812
to
69dd72f
Compare
@FloatingFowl Thanks a lot for your work on this! I've been working on other projects and had forgotten about this PR, so I apologize for merging it after such a long time. Thank you for your patience 🙂 |
I've merged this in the |
All class (public) members have been documented (including the operators) along with the other helper/utility functions present in
include/functions
. Openingdocs/html/index.html
in a browser will give the documentation.To regenerate the documentation, run
cd docs; doxygen Doxyfile
from the root directory after installing Doxygen.Currently the documentation must be updated manually. The next step can be to integrate it with Travis.CI and possibly link to the documentation from the repo website.
Closes #4.