Removals from model are never relayed using model relay system
Description
Environment
Activity

Cindy LiJanuary 6, 2017 at 3:28 PM
The pull request https://github.com/fluid-project/infusion/pull/577 has been merged into the infusion repo master branch at 07cc0d5ba6fe85a4b910751c9db8cec6c501e3bc
Tony Atkins [RtF]October 26, 2016 at 8:13 AM
In later discussions it was agreed that it wouldn't be fixed in 2.0: https://github.com/fluid-project/infusion/pull/577#issuecomment-255371232
I see that put the right "Affected Version" back in already, so we're good to go.

Justin ObaraOctober 25, 2016 at 1:13 PM
the current intention is that this will be fixed for the Infusion 2.0 release, although that may change based on some discussions today. If the plan is changed, it will be reverted back to affecting 2.0 and the fix for removed or set to some future version.
Tony Atkins [RtF]October 25, 2016 at 11:34 AM
, I'm not sure why you changed the affects version, perhaps to get it off of some rollup list? IMO it would be better to set the "Affects Version" to a recent release, and to set the "Fix Version" once a release with a verified fix is available.
Tony Atkins [RtF]October 17, 2016 at 11:54 AMEdited
Hi, and . I have recently been bitten by this problem, as the gpii-binder uses the "DELETE" type to clear out model variables when form inputs are cleared.
Check out this example for a disturbing variation on the problem:
This results in output like the following:
Please note that on the next subsequent change to the child model, the variable that was deleted in the parent is recreated in the parent with the original value. This is the kind of thing that is likely to come up often in even moderately complex groups of components that use the binder.
I could use a pairing session to discuss this, if there is no one working on it, I will likely need to address this before my work with the UL can continue.
Details
Assignee
Antranig BasmanAntranig BasmanReporter
Cindy LiCindy LiComponents
Priority
Major
Details
Details
Assignee

Reporter

When using "fluid.transforms.free" to relay the model change to the target, the removal from the source model doesn't get relayed.
For example, if the initial model starts with:
{
a: true,
b: true
}
Then, modify the model to
{
a: true
}
The modification doesn't get relayed to the target.