-
Notifications
You must be signed in to change notification settings - Fork 35
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
docs: add documentation for BFS (#56) #73
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.
Hi there! Thank you for creating your first pull-request on the Graaf library :)
Codecov ReportPatch coverage has no change and project coverage change:
Additional details and impacted files@@ Coverage Diff @@
## main #73 +/- ##
==========================================
- Coverage 99.73% 99.67% -0.07%
==========================================
Files 23 23
Lines 1140 1226 +86
==========================================
+ Hits 1137 1222 +85
- Misses 3 4 +1 ☔ View full report in Codecov by Sentry. |
Thanks for your contribution 🚀 |
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.
Hi @MichaeINeumann thank you for the contribution! The section looks very detailed and provides very good examples of BFS use cases.
Only one comment on the Syntax
section, let me know what you think and we can merge it 🚀
Co-authored-by: Bob Luppes <bobluppes@gmail.com>
a/b/c was displayed in one line
Thanks, LGTM 👍🏻 |
Hello, I made the documentation for BFS.
Please Check the ## Syntax section. I understood not exactly what I did here.
Also I'm not sure with the content at ### BFS is particularly useful for: , because I not used this algorithms in praxis.
I have only experience with dijkstra in robot programming.