-
-
Notifications
You must be signed in to change notification settings - Fork 424
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
Add docstrings for a few small modules! #286
Conversation
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.
Okay, here we go! Some initial comments for this effort, which I suppose is a monotonic improvement over no documentation. :-) Thanks for stepping up!
@Be-ing thanks! I have fixed the issue. |
eb8ad2d
to
7abdccc
Compare
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.
Getting there!
4df8902
to
a1ea3af
Compare
01eebe8
to
9872e21
Compare
9a476fa
to
3206468
Compare
- Add module docs for the `libsignal_protocol` crate! - Add docs to the `device-transfer` crate! - Add docs to `address`! beef up the docs for `address` because this is an important struct! respond to review comments revert module visibility changes de-clutter the docstring for `.device_id()` add missing docs warning fix uuid deps add doctest for `ProtocolAddress::new()`! avoid pulling in uuid into dev-dependencies
Ah, right, some doc comments will make it into the generated C header for Swift. You can run |
Added the generated swift ffi changes! |
Problem
This is the first in a set of planned PRs to add inline documentation to the Rust API which can then be beautifully published with
cargo doc
. See #285.I am not a Signal engineer. I am making my best guesses as to the appropriate docstring content. I think I've been able to do just fine, but please push back if I'm mischaracterizing anything -- it's easy for me to just revert anything that seems possibly too bikesheddable.
Solution
libsignal_protocol
crate.device_transfer
crate.address
module.Result
We will have established a rapport for further improvements to the documentation and module layout as per #285!