Graph.paste_nodes() returns pasted node instances #309
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi,
is there a reason why
paste_nodes()does not return node instances likeduplicate_nodes()does? This small change takes care of that.I find this possibility useful, because I am able to emit the
node_createdsignal on those nodes and am able to check whether instances of the same type already exist in the graph and if so, to prevent pasting/duplicating of those nodes (in my application it does not make sense for certain nodes to be in the graph more than once...). That begs the question: shouldn'tpaste_nodes()andduplicate_nodes()emitnode_createdby default?