Uploaded image for project: 'Fluid Infusion'
  1. Fluid Infusion
  2. FLUID-4935

resolverSetConfig option is not propagated from the renderer component grade to its applier.

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 1.5
    • Component/s: Data Binder
    • Labels:
      None

      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]
      }

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              jobara Justin Obara
              Reporter:
              yura Yura Zenevich
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: