Details
-
Improvement
-
Resolution: Fixed
-
Major
-
None
-
None
Description
An exception should be thrown when attempted to get unknown modules.
Care needs to be taken - some code checks if a module is present (see InstallContext for instance) - but ideally the methods of ModuleRegistry should be consistent in how they treat absent module. Maybe we'll need to expose a new method to check for modules' existence.
For 4.1 we'll simply issue a warning to avoid breaking the api.
Checklists
Acceptance criteria
Attachments
Issue Links
- is depended upon by
-
MGNLNEWSLETTER-4 Fix renaming issue
-
- Closed
-