Description Jan Christoph Ebersbach 2016-06-06 11:47:24 CEST

The import hook mechanism of ucs@school-import-tool is tied to the implementation of a single class method.  This leaves error handling and execution order up to the customer.  Furthermore, reusability is highly reduced because the class method can't be integrated in other classes.

I'd find it optimal if there were a mechanism that would allow customers to register arbitrary functions as hooks.  Through a well defined interface these methods are automatically called once a hook point is reached.  These functions could be shipped with UCS@school or shared between customers.  The integration/activation is done at the liking of a specific customer.  The old hook mechanism that made use of run-parts was very much like the mechanism described here except that the new mechanism solely relies on Python code.