fix: Ctrl+D inside a layer's sub-graph causes the parent layer to be placed inside itself#3811
Conversation
…placed inside itself
Summary of ChangesHello @Annonnymmousss, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request addresses a critical bug related to layer duplication within sub-graphs. Previously, duplicating a layer using Ctrl+D while inside a sub-graph would result in an erroneous placement of the parent layer within itself. The fix ensures that all relevant layer manipulation functions correctly account for the active sub-graph context, preventing this invalid document structure and improving the reliability of the duplication feature. Highlights
Changelog
Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here. You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension. Footnotes
|
There was a problem hiding this comment.
Code Review
This pull request addresses a bug that occurs when duplicating layers within a subgraph. The fix correctly scopes the duplication logic to the current network context by passing self.selection_network_path to shallowest_unique_layers, upstream_flow_back_from_nodes, and copy_nodes. The changes are consistent and effectively resolve the issue. The code is clean and the fix is well-targeted. Great work!
Closes #3809