-
Notifications
You must be signed in to change notification settings - Fork 27
Install and uninstall have different casing sensitivities #1116
Copy link
Copy link
Open
Labels
Description
Describe the bug
If module.xml defines a package as MyPackage.MySubPackage.PKG but the actual classes are MyPackage.MySubpackage.MyClass.cls, then install will work just fine, but uninstall will fail to find the classes and fail to remove them. Uninstall will actually succeed without any errors in this case.
To Reproduce
Steps to reproduce the behavior:
- Define a module.xml with a package resource like
MyPackage.MySubPackage.PKG - Include classes like
MyPackage.MySubpackage.MyClass.cls, with the casing difference - Load the module
- Uninstall the module
- Note the classes don't get deleted
Expected behavior
The classes get deleted even though the case is different
System information (please complete the following information):
- IPM version: 0.10.6
- IRIS version: Unknown
- OS: Unknown
- Docker or local: Unknown
Workaround
Ensure your package and classes are actually named with the same case.
Dev notes
%IPM.Storage.ResourceReference.GetChildren() uses %Library.RoutineMgr_StudioOpenDialog, which is case-sensitive. We should replace with a query on %Dictionary.ClassDefinition instead.
Reactions are currently unavailable