Affects Version/s: 1.5
Fix Version/s: None
Currently there's not support for a wildcard mergePolicy.
For example we would like to be able to declare the following policy:
Which would result in no expansion for every second level (in the tree) "someObject" object.
The issue first arose in GPII's lifecycle manager where we used now removed non-api function fluid.resolveEnvironment. We switched to using fluid.expand that acts almost in the same way. The noticeable difference between the two was that the latter one actually knows how to handle expanders (unlike the former).
The object that was expanded with fluid.expand contains expanders but in the path that should not be expanded by the utility. Thus we were required to write an optional mergePolicy that would indicate that that particular path doesn't need to be expanded.
Currently in order to do that we have to express it with an expanded version of the mergePolicy:
Example of the expanded material: