Document behavior whan adding Node to a Graph with already used identifier #13
Labels
No labels
Complexity/Higest
Complexity/High
Complexity/Low
Complexity/Lowest
Complexity/Normal
Importance/High
Importance/Highest
Importance/Low
Importance/Lowest
Importance/Normal
Kind/Bug
Kind/Documentation
Kind/Feature
Kind/Structure
OS/Linux
OS/MacOS
OS/Windows
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
linarphy/galaxy-graph#13
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Right now, a node will fail to connect if it has an identifier that is already defined in the graph. I think this could be better if we re-use the node in this case. But I’m not sure about user expectation in this case. Would that surprise user to use a different object in the connection than the one they used in the connect method ?
Current behavior is
NodeAlreadyInGraphError, which may be fine already.After some though, I think current behavior is good. May be good to add documentation about this just in case. If this is applied, user could do
Re-use Node with existing identifier in graph.connectto Document behavior whan adding Node to a Graph with already used identifier