Details
Assignee
Antranig BasmanAntranig BasmanReporter
Antranig BasmanAntranig BasmanComponents
Affects versions
Priority
Major
Details
Details
Assignee
Antranig Basman
Antranig BasmanReporter
Antranig Basman
Antranig BasmanComponents
Affects versions
Priority
Created November 16, 2016 at 11:56 PM
Updated November 16, 2016 at 11:57 PM
Our support for issuing changes via the ChangeApplier in the IoC testing framework is rather old-fashioned and has a syntax which dates from before the https://fluidproject.atlassian.net/browse/FLUID-5024#icft=FLUID-5024/https://fluidproject.atlassian.net/browse/FLUID-5114#icft=FLUID-5114 model relay rewrite. It still exposes access to the applier's
modelChanged
event which should really be an implementation detail, as in:{ listenerMaker: "fluid.tests.makeChangeChecker", makerArgs: ["{asyncTester}.options.furtherTextValue", "textValue"], // alternate style for registering listener spec: {path: "textValue", priority: "last"}, changeEvent: "{asyncTest}.applier.modelChanged" },
We should normalise this syntax to conform with the standard one for triggering changes in the new(er) declarative framework as per http://docs.fluidproject.org/infusion/development/ChangeApplierAPI.html#declarative-style-for-triggering-a-change