This fixes a design problem where custom topologies weren't able to access components loaded from plugins, due to the fact that the custom topology needs to be created before JApplication::Initialize() gets called, which includes plugin loading. We add a new setter that accepts a lambda for configuring a topology after the plugins have loaded.
Briefly, what does this PR introduce?
This fixes a design problem where custom topologies weren't able to access components loaded from plugins, due to the fact that the custom topology needs to be created before JApplication::Initialize() gets called, which includes plugin loading. We add a new setter that accepts a lambda for configuring a topology after the plugins have loaded.
What kind of change does this PR introduce?
Please check if this PR fulfills the following:
Does this PR introduce breaking changes? What changes might users need to make to their code? No.
Does this PR change default behavior? No