-
Notifications
You must be signed in to change notification settings - Fork 482
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
Docstring updates #921
Docstring updates #921
Conversation
This should be ready for review now. |
@@ -127,7 +127,7 @@ H3Error H3_EXPORT(areNeighborCells)(H3Index origin, H3Index destination, | |||
* destination | |||
* @param origin The origin H3 hexagon index | |||
* @param destination The destination H3 hexagon index | |||
* @return The directed edge H3Index, or H3_NULL on failure. | |||
* @param out Output: The directed edge H3Index. |
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.
Should we include the @return
still for the H3Error
path?
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.
Eg, just copy this from further below:
* @param out Output: The directed edge H3Index. | |
* @param out Output: The directed edge H3Index. | |
* @returns E_SUCCESS on success, or another value on error |
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.
I was most focused on ensuring the docstring wasn't incorrect, rather than completing it. That seems like a good addition.
This updates the doc strings in a few places to be consistent with the actual parameters. I also changed Doxygen settings to improve that a little, e.g. to include the public API header.
Based on #919, #920.