Record related_class used by ReactiveCachingWorker
From #34 (comment 285445781), the problem we have with ReactiveCachingWorker right now is that it's polymorphic: it's used by many different concrete classes, potentially with different requirements and different execution profiles.
To track this, we'll add a new allowed metadata key in LabKit: related_class
. This class is up to the user to define and by default is blank. For ReactiveCachingWorker
(and other polymorphic cases like DeleteStoredFilesWorker
), this can be the 'actual' class; for other cases, it can be something different.
Edited by Bob Van Landuyt