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.
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
Node grouping API #4427
Node grouping API #4427
Changes from 7 commits
2ff33b2
0d6461a
ef4d664
a299ef3
b79f1f5
a8b1f45
9d736b9
5e0bc8c
ada46e6
cee4a2c
78e54f3
ae435ca
c7278ff
172a951
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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 think we have O(Nˆ2) complexity here, as every time we add a node, we recreate a list based on what was already there. So maybe it makes sense to initialize
grouped_nodes[key]["nodes"]
and then just append to 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.
You mean when essentially every node would be in a separate group? Maybe we can get around that by checking straight away if there are any namespaces in the pipeline and if not just return all nodes separately.
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 mean just don't unpack the list but rather append to it, like
Nothing should change structure-wise from the current implementation.
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.
But maybe we should also check if there are any namespaces at all. Don't know without looking into the code if that's easy. If there are no namespaces in the pipeline at all, it doesn't make sense to call this method and the user should probably be made aware.
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.
Added the suggestion by @ElenaKhaustova
@merelcht
Even to check for namespaces, I believe we'd have to check all the nodes for
node.namespace
- if the node doesn't have a namespace, it's treated as its own group. Maybe this check belongs on the plugin side?