Modifications to network, zoning or other core components should be handled via a seaprate modifier class to ensure ids remain consistent
Idea: use a modifier class for "big" changes that afefct multiple entities (nodes,links, etc.). Any changes, especially deletions require updating of ids and indices that should be hanlded here without the user knowing about it.
The modifier can use the unlerying builder to make changes, create enw entities, etc.
Modifications to network, zoning or other core components should be handled via a seaprate modifier class to ensure ids remain consistent
Idea: use a modifier class for "big" changes that afefct multiple entities (nodes,links, etc.). Any changes, especially deletions require updating of ids and indices that should be hanlded here without the user knowing about it.
The modifier can use the unlerying builder to make changes, create enw entities, etc.