-
Notifications
You must be signed in to change notification settings - Fork 0
docs: Update data logging. #1
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
@microbit-mark this is ready for review and merge, which should update upstream PR bbcmicrobit#720. |
8da4ce9
to
ecaa719
Compare
docs/log.rst
Outdated
flash storage. If set to ``False`` it uses a "fast" method, | ||
which invalidates the data instead of performing a slower | ||
full erase. | ||
There are two erase modes, "full" completely removes the data from the |
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 wonder if this is more explicit about the two modes?
There are two erase modes, "full" completely removes the data from the | |
There are two erase modes; "full" completely removes the data from the physical storage and "fast" which invalidates the data without removing it from the storage. |
docs/log.rst
Outdated
add(key=value) | ||
|
||
There are two ways to add a data row into the log: | ||
:param full: ``True`` selects a "full erase" and ``False`` selects the |
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.
Rather than having quote marks for "full erase", just quote the mode names "full" and "fast" as it will be more consistent in help docs
:param full: ``True`` selects a "full erase" and ``False`` selects the | |
:param full: ``True`` selects a "full" erase and ``False`` selects the "fast" erase method. |
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.
A couple of suggested edits, otherwise LGTM to merge
Thanks Mark! Implemented the comments in e8069e4 |
@microbit-mark FYI I'll be adding some updates to the datalog docs here (a PR to your fork), once it's ready we can merge it and the upstream PR will be updated and ready for merge into the upstream v2-docs branch.
First commit is just formatting right now, will add more things later.