-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Examples: Add proper Table of Contents #20957
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.
Didn't have time to do a throughout review but already found little issues.
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.
Will improve things mentioned, thank you for the review :)
@AnnsAnns do you think it would be possible to include a basic static test that goes over the directory list in |
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.
Thanks for your work on this! Just had a brief look and left some comments below.
Could we maybe have a two-column table-style of the list? At least, I would argue for moving the explanation from the single subitem to the item itself, potentially after a colon (:
).
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 think that there is a little typo for timer_periodic_wakeup
and this file should be named README.md not README:md (period instead of colon).
Looking into it, should be feasible :) |
Added (Even found a few missing entries thanks to it 😅) |
I hope I covered all mentioned issues, let me know if there is anything else :) I also changed it to a table format as mentioned by @mguetschow, it definitely looks better on github |
Nice! I am happy with it. There's one static test that you should fix. A nit pick could be to combine the two ci tests into one, reducing the burden on the servers but I believe that is not significant here. |
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.
Looks good, thank you!
Would you mind squashing the commits together? |
examples: ToC about all examples examples: Fix whiteline issues examples: Improve wording of Rust example Co-authored-by: Teufelchen <[email protected]> examples: Reduce redundant wording Co-authored-by: Teufelchen <[email protected]> examples: remove mention of repository Co-authored-by: Teufelchen <[email protected]> examples: Improve wording of coap example text Co-authored-by: Teufelchen <[email protected]>
examples/readme: fix SAUL spelling mistake examples/readme: Link to README.md instead of folder examples/readme: increase title size examples/readme: make networking category name a bit clearer examples/readme: move nimble to own category within BLE examples/readme: move dtls to own category examples/readme: move heart rate sensor to nimble category examples/readme: move arduino sketch to languages examples/timer_periodic: fix file name issue examples/readme: change level wording about nanocoap
688a8fa
to
a7e8c32
Compare
examples/readme: add missing entries examples: document examples with no readme
Did you maybe accidentally drop some commit?
|
examples: Remove whitespace to fix CI
a7e8c32
to
cd076d4
Compare
Fixed, sock_tcp_echo was a new example (and pio_blink went missing) |
Congrats! It's really awesome! |
Contribution description
Currently there is no description of the examples (Some not even having a README).
This PR aims to add a basic table of contents README for the examples directory to improve the UX when searching for examples while also adding a few minor READMEs for undocumented examples.
It also tries to improve the general readability of the folder by categorizing examples into easier to digest categories within the README. This makes specific examples easier to find.
Testing procedure
There are no changes within this PR that would affect the code.
Issues/PRs references
This aims to help with some of the issues mentioned within #20388