-
Notifications
You must be signed in to change notification settings - Fork 8
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
Fix delete_node to allow breaking cycles in graphs. #75
Conversation
Codecov Report
@@ Coverage Diff @@
## main #75 +/- ##
==========================================
- Coverage 65.59% 65.12% -0.47%
==========================================
Files 113 114 +1
Lines 6162 6220 +58
==========================================
+ Hits 4042 4051 +9
- Misses 2120 2169 +49
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it 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.
я бы еще параметр clean_up_leftovers
у метода disconnect_nodes
по дефолту убрала в False
Но кажется, что дефолтное поведение Представим граф:
Допустим, мы пытаемся удалить узел 4 с прямыми потомками. Пошагово:
Реконнекта так и не произошло, случилась кака Возможно, стоит в этом месте использовать Этот момент легко проморгать в будущем, если станем использовать эту опцию |
Поправил, хорошо что заметил, тонкий момент! |
Previously they were automatically preserved because parents were always reconnected to children.
This change is backward compatible except for 1 rename (
RemoveType.node_only -> RemoveType.node_rewire
), no current behavior is altered.Related to #69 where cycles that appeared in graph precluded optimization from removing accidental cycles.