Override module collection path on code import
Override module collection path on code import
Article summary
Did you find this summary helpful?
Thank you for your feedback
You now have the option to override the module collection path on page import. This is useful for when you have to override paths for languages which do not explicitly define a path, for example Python.
Additionally, you can use this feature for when you have classes that have the same name, but do not belong to the same package, and you do not want them to be merged when they are imported in to Quality Modeller.