FLUID-4935: resolverSetConfig option is not propagated from the renderer component grade to its applier.

Description

The renderer component grade currently supports resolverGetConfig and resolverSetConfig options that would allow its user to customize parsing, accessing and setting strategies for it's data model.

However in case a user wants to customize a settings strategy, the actual set configuration is not propagated from the renderer component to its applier that handles the actual change requests.

The particular use case arose when we attempted to customize such configs for a model that contains escaped "." characters. Instead of the default parser attempting to parse the escaped "."'s as segments in the elPath, we wanted (to no success) to ignore them and use the whole key as a whole.

Example of the model:
{
"http://registry.gpii.org/applications/org.gnome.orca": [{
value: {
rate: null
}
}]
}

Example of the valuebinding:
"${http://registry\\.gpii\\.org/applications/org\\.gnome\\.orca.0.value.rate}"

Custom config would need to look like this:
{
parser: {
parse: fluid.pathUtil.parseEL,
compose: fluid.pathUtil.composePath
},
strategies: [fluid.model.defaultFetchStrategy, fluid.model.defaultCreatorStrategy]
}

Comments

• y z commented 2013-03-15T00:27:54.698-0400

  A fix strategy involves the following:
  Update renderer component grade's default mergePolicy and add a reference from changeApplierOptions.resolverSetConfig option to the top level resolverSetConfig option.

• Antranig Basman commented 2013-03-15T00:59:26.256-0400

  Note that this test case itself has now created a THIRD place where this configuration is copied in the framework. When FLUID-4933 is resolved, we must remember to catch this location too

• Antranig Basman commented 2013-03-15T01:01:15.186-0400

  Thanks for the report, test case and fix, Yura - pushed to master at 46eff4c