Carlton Whitehead02/11/2020, 3:22 PM
, to obtain a new instance of a
each time? I'm finding it a bit clunky and error-prone to build out the
such that it expects a
with its dependencies graph prepared. Making the `Wizard`'s
know about all the wizard pages dependencies, those pages dependencies' dependencies, and so on is what makes it feel clunky to me. Is there a way
could act as a factory instead of as a singleton lookup? I feel like that would really simplify this. Is that possible?
results in getting the same wizard each time, with old values left-over from prior use.
Romanow02/12/2020, 12:08 AM
Carlton Whitehead02/12/2020, 12:10 AM
might be the answer. Inside the wizard could use that to make sure its dependences don't linger in the scope, without having to go to the trouble of setting up or tearing down a new scope.
method is warranted after all. I'm going to experiment with that offline some and will file a ticket if it seems to pan out.