-
Notifications
You must be signed in to change notification settings - Fork 59
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
Composite nodes version 2 #867
Comments
This issue is stale because it has been open for 6 months with no activity. Consider reviewing and taking an action on this issue. |
Until composite nodes gets used in anger I'm tempted to close this and move it to the wiki backlog. |
This issue is stale because it has been open for 6 months with no activity. Consider reviewing and taking an action on this issue. |
Closing this ticket and adding to the Brainstorm Ideas List. |
Prerequisites
Help
>Support Package
Description
We've identified issues with composite nodes on large graphs (especially those with a lot of transactions) and unexpected behaviours when you copy composite nodes between graphs.
The existing version will remain an experimental feature with a plan to create a newer version from lessons learned. Re-writing is the way to go because trying to fix the issue created other problems.
With the current implementation the approach was to go with a "light" implementation which means it didn't affect the structure of the core graph. This has created limitations so with the new version we will be creating a composite node element on the graph which will require an update to the schema.
The text was updated successfully, but these errors were encountered: