Skip to content

Same named GUID suffixed object isn't renamed after the original object is removed #51

Description

@Biraru

Describe the bug
When an object is created with a GUID suffix (e.g. objectName_GUID) to avoid a naming conflict, removing the original object (objectName) does not cause the GUID-suffixed object to be renamed back to objectName.

To Reproduce

  1. Create an object named Script.
  2. Create another object with the same name so it is automatically renamed to Script_GUID.
  3. Delete or remove the original objectName.
  4. Observe that the remaining object keeps the objectName_GUID name instead of being renamed to objectName.

Expected behavior
Once the original objectName is removed, the remaining oldest same named object should be renamed from objectName_GUID back to objectName, as the naming conflict no longer exists.

Screenshots
Image
Image

Desktop (please complete the following information):

  • OS: Windows 11 Pro 64-bit
  • Azul Version: V44

Additional context
The GUID suffix is only intended to prevent name collisions. When the conflicting object no longer exists, the suffix should be removed automatically to restore the object's intended name.

Metadata

Metadata

Assignees

Labels

bugSomething isn't working

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions