art 3.02.04 constructs modules that are not included in paths
Although the workaround includes using the
--prune-config program option, this error should be fixed.
#2 Updated by Kyle Knoepfel 7 months ago
- % Done changed from 0 to 100
- Status changed from Assigned to Resolved
The fix was implemented with commit art:f58a81. It involved transferring some of the information from the configuration-pruning system to the path manager. By doing this, the framework is actually more permissive about the allowed configuration. For example, the framework now allows a user to specify (e.g.)
as long as
BadModuleConfig does not appear on a trigger or end path. This varies wrt. previous behavior, where a
module_type parameter, at minimum, was required, even if the configuration was ignored. Additionally, any libraries corresponding to modules that are not used by the framework are no longer loaded, which also varies wrt. previous behavior.
The fix unfortunately introduces an undesirable coupling in the
PathManager test between the
PathManager class and the configuration-pruning facilities. This coupling should be removed, which is described in issue #22439.