-
Notifications
You must be signed in to change notification settings - Fork 53
Added documentation for modes #52
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
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.
Please explain what you mean by not cooperating. It'd be best to document them where they are define.
| ``sensor.mode = adafruit_bno055.ACCONLY_MODE`` | ||
| replacing ``ACCONLY_MODE`` with the mode you want to use | ||
|
||
.. data:: CONFIG_MODE |
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.
Does this render it on the module or class?
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.
@tannewt So I wasn't able to get it to render that way. I'm not sure why, but I'm not very experienced with autodoc or sphinx, so there's probably a way to do it that I just don't know about. I tried putting comments with |
@dherrada I use this tool to make tables for RST docs: I'll look for an example of when I used it.. 👀 |
@siddacious I think there may be an example in this library already. The issue I'm currently running into is that it'd be better to document the modes where they are defined, but I can't figure out how to tell sphinx to do that.
|
Oh... Huh. I wonder why it didn't work like that here Edit: looks like they need a line on the top and bottom to work right |
So if you did a triple quoted comment after the definition it didn't work? That may be a class member thing only. |
Yeah, I think that may be the case |
@tannewt Moving forward, what would you like me to do with this PR? I know the way I have it isn't really ideal, but I'm not quite sure how else to do it. |
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.
This is fine. I don't want to block you on adding documentation even if the location is less than ideal.
Updating https://github.com/adafruit/Adafruit_CircuitPython_BNO055 to 5.1.0 from 5.0.2: > Merge pull request adafruit/Adafruit_CircuitPython_BNO055#52 from adafruit/docs-update > Merge pull request adafruit/Adafruit_CircuitPython_BNO055#54 from adafruit/i2c-gpio_example Updating https://github.com/adafruit/Adafruit_CircuitPython_Fingerprint to 2.0.0 from 1.2.2: > Merge pull request adafruit/Adafruit_CircuitPython_Fingerprint#21 from jerryneedell/jerryn_fingersearch Updating https://github.com/adafruit/Adafruit_CircuitPython_BLE to 7.0.3 from 7.0.2: > Merge pull request adafruit/Adafruit_CircuitPython_BLE#95 from madgrizzle/patch-2 Updating https://github.com/adafruit/Adafruit_CircuitPython_Pypixelbuf to 2.1.2 from 2.1.1: > Merge pull request adafruit/Adafruit_CircuitPython_Pypixelbuf#26 from dunkmann00/dotstar-brightness Updating https://github.com/adafruit/Adafruit_CircuitPython_ServoKit to 1.3.0 from 1.2.2: > Merge pull request adafruit/Adafruit_CircuitPython_ServoKit#21 from razvanphp/master
@tannewt This should clear up #16. I tried to document them where they were defined, but sphinx was not cooperating