You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Just would like to understand if there is any particular reason to do not have an overload of the GroupModel constructor accepting the id as parameter.
If you serialize the diagram nodes in a Json format , when recreating the diagram from the json payload you need to create additional logic to update the id of the groups in all child elements in your Json and refactor all the links based in the new id.
That's additional processing time that could be avoided by just allowing us to set the Id of the GroupModel when instantiating it from Json.
If there is no particular reason for that, could we have this added in the next release?
I don't think it will be a big change, since the GroupModel inherits from NodeModel, which already have the id parameter in the constructor.
The text was updated successfully, but these errors were encountered:
Hello,
Just would like to understand if there is any particular reason to do not have an overload of the GroupModel constructor accepting the id as parameter.
If you serialize the diagram nodes in a Json format , when recreating the diagram from the json payload you need to create additional logic to update the id of the groups in all child elements in your Json and refactor all the links based in the new id.
That's additional processing time that could be avoided by just allowing us to set the Id of the GroupModel when instantiating it from Json.
If there is no particular reason for that, could we have this added in the next release?
I don't think it will be a big change, since the GroupModel inherits from NodeModel, which already have the id parameter in the constructor.
The text was updated successfully, but these errors were encountered: