Sometimes we have Jobs that refer back up the same stack to a parent TaskDriver.
However, that parent TaskDriver isn't fully initialized yet so it will have null references or be a null reference itself depending on how you get access to it.
As a work around you can call a custom method on your TaskDriver after you instantiate it but that's a bit cumbersome.
A better solution would be to have all TaskDrivers implements an Abstract method to configure their jobs. This method will be called on all TaskDriver's right before Harden is called.
This would ensure the same macro order of operations happens but that the entire chain of relationships (parent and sub taskdrivers) and their data is initialized and ready to go.
Sometimes we have Jobs that refer back up the same stack to a parent TaskDriver.
However, that parent TaskDriver isn't fully initialized yet so it will have null references or be a null reference itself depending on how you get access to it.
As a work around you can call a custom method on your TaskDriver after you instantiate it but that's a bit cumbersome.
A better solution would be to have all TaskDrivers implements an
Abstractmethod to configure their jobs. This method will be called on all TaskDriver's right beforeHardenis called.This would ensure the same macro order of operations happens but that the entire chain of relationships (parent and sub taskdrivers) and their data is initialized and ready to go.