Skip to content

More graceful handling of not-found modules

Christian Dreher requested to merge fix/module-not-found-handling into main

"module not found" errors are very discruptive and can often only be fixed by manually editing configuration files. Sometimes even module descriptions of some dependencies etc. This fix tries to be more graceful with the handling of not-found module descriptions by displaying it, but still proceeding with normal operation. It will be displayed to the user so that they can react. But often it is enough to just update the workspace in order to fix such issues.

Exception: module databases => TODO: Identify that a module belongs to the authority of a module database and add explicit dependencies so that module database is set up before the module is addressed. This would require to reload module definitions after updating module databases.

Not implemented yet: "axii w g s" and similar not working (quitting early without error message) => not happening anymore

Edited by Christian Dreher

Merge request reports

Loading