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:
Example of the valuebinding:
Custom config would need to look like this:
strategies: [fluid.model.defaultFetchStrategy, fluid.model.defaultCreatorStrategy]