-
Notifications
You must be signed in to change notification settings - Fork 18
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
Enable renaming object name from Object Tree #619
base: main
Are you sure you want to change the base?
Conversation
40cb877
to
381c840
Compare
Integration tests report: appsharing.space |
Preview PR at appsharing.space |
There's a small issue |
should the rename input be activated with a single click? And you need to propagate the change to all downstream operators. |
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.
Thanks a lot for starting this! 🚀
I believe we should tackle #200 first.
objectName as string | ||
); | ||
if (obj) { | ||
this.props.cpModel.sharedModel?.updateObjectByName( |
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.
We not only need to update the specific object, but we also need to go through all objects and see if they depend on it. All objects have a dependency
parameter which is a list of object it depends on, by name. And operators are applying their operation based of the objects names.
I believe it's easier to tackle this renaming task once #200 is done. We wouldn't need to do that work I'm describing above because the list of dependencies would be a list of UUIDs. And operators would be defined based of UUIDs.
I would suggest we put this renaming PR on hold while #200 is not tackled.
Thanks @trungleduc |
Shall close #609
rename.mov