wirebox q -- I'd like to modify an object after it...
# box-productsd
David Rogers
09/14/2022, 2:15 PMwirebox q -- I'd like to modify an object after it is fully created by the wirebox binder, including after onDiComplete; I thought an influence closure would do this, but it runs before onDiComplete; is there an instance creation hook like this? Maybe just somehow mock out onDiComplete itself?
David Rogers
09/14/2022, 2:16 PMultimate usecase here is "appendVirtualAttribute" on a quick instance in tests
b
bdw429s
09/14/2022, 2:17 PMafterInstanceCreationbdw429s
09/14/2022, 2:17 PMd
David Rogers
09/14/2022, 2:18 PMah the old "shoulda read the docs"
b
bdw429s
09/14/2022, 2:18 PMYour interceptor will fire for ALL instance, so it's up to you to check which instance is being created and then conditionally modify it if needed.
d
David Rogers
09/14/2022, 2:18 PMyeah all instances of a particular binding is the goal
David Rogers
09/14/2022, 2:21 PMah I see, it's per injector. I can make that work. Would be cool if there was a per binding hook for that though.
b
bdw429s
09/14/2022, 2:27 PMI can see the utility, but it also could be seen as feature bloat since we already have a more generic solution.
bdw429s
09/14/2022, 2:27 PMPerhaps put in a ticket though to be able to provide an
afterCreationbdw429s
09/14/2022, 2:27 PMThe influence closure was really designed to allow you to modify the mapping itself on the fly, and the mapping is really just the "recipe" for how to build the instance.
bdw429s
09/14/2022, 2:28 PMSo in other words, the influence closure is like a recipe card that can auto-tune the amount of eggs in the cake before you cook it, but the afterinstancecreation is like the food prep guy who adds the candles on every finished cake they go out the kitchen door.
s
sknowlton
09/14/2022, 2:29 PMbrad with the programming bakery analogy ftw
d
David Rogers
09/14/2022, 2:30 PMhm...I think the influence closure is provided the cake, in the above analogy?
Copy code
var result = influenceClosure( instance = oModel, injector = this );David Rogers
09/14/2022, 2:30 PMmaybe I misunderstand
b
bdw429s
09/14/2022, 2:33 PMI was thinking the influence closure ran prior to the instance being done building, but perhaps not
bdw429s
09/14/2022, 2:33 PMYou said this above
I thought an influence closure would do this, but it runs before onDiComplete
bdw429s
09/14/2022, 2:34 PMLooking at the code however, are you sure that is true?
bdw429s
09/14/2022, 2:34 PMIt does appear to happen very near the bottom of the getInstance() method.
d
David Rogers
09/14/2022, 2:35 PMpretty sure ... did a writedump "influence" and a writedump "onDIComplete" in target obj... let me do that again ....
b
bdw429s
09/14/2022, 2:35 PMNow that I look at the code, I'm fairly sure ondicomplete should run prior to the influence closure, just scanning the code
bdw429s
09/14/2022, 2:35 PMBecause onDiComplete should run as part of ther
builder.buildCFC()bdw429s
09/14/2022, 2:37 PMCrap, we're gonna need a new analogy... ok the influence closure is no longer a sentient recipe card, it's now an elf on the shelf that pops out of the bag of flour at some unknown time and sticks his finger in the icing. 🧝
s
sknowlton
09/14/2022, 2:41 PMbest coldbox internals thread ever
3 Views