-
Notifications
You must be signed in to change notification settings - Fork 54
Improve docstrings #944
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
Improve docstrings #944
Conversation
✅ Deploy Preview for neo4j-graph-data-science-client canceled.
|
@FlorentinD The two top commits on this PR are from me, so I am not sure if it makes sense for me to review. But I can rebase to make this more apparent. |
122c599
to
29bf543
Compare
- Content copied as much as possible from GDS Manual - Add default values
- Content copied as much as possible from GDS Manual - Add default values
5e80e0f
to
68c233b
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.
nice cleanup
one small comment
Runs the Articulation Points algorithm and stores the results in the graph catalog as a new node property. | ||
Given a graph, an articulation point is a node whose removal increases the number of connected components in the graph. | ||
The Neo4j GDS Library provides an efficient linear time sequential algorithm to compute all articulation points in a graph. |
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.
do we want to refer here to the Neo4j GDS Library?
IMO, we can skip the last sentence as well.
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 agree, can take this away.
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 reading through 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.
I was thinking when I did this that I didn't want to deviate from the GDS manual because then there'd be two sources of truth. So I have only copied lines, but the amount of copying is varying. I was thinking that having nice one-liners and one-paragraphers to describe the algorithm is a useful thing also in the manual itself, but I didn't want to scope creep too much. So I think just taking some verbatim content from the manual is my current approach
PR build failures are not specific to this PR. |
Co-authored-by: Florentin Dörre <[email protected]>
Based on #942ref GDSA-233