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

Revert behaviour of model transforms which automatically assume that nested value is a transform

    XMLWordPrintable

Details

    • Bug
    • Status: Open
    • Major
    • Resolution: Unresolved
    • None
    • None
    • None

    Description

      Since the beginning of the implementation of the system, this semantic choice has simply caused frustration, surprise, and annoyance. It is simply NEVER the case that the person writing:

                  transform: {
                      type: "fluid.transforms.condition",
                      condition: {
                          transform: {
      ....
                          }
                      },
                      "false": {
                              value: "Congratulations, you are a genius",
                          }
                      }
      

      expects that the key "value" is intended to be considered a path index into the document. They ALWAYS consider that the argument supplied to "false" etc. is a literal value to be output into the document - UNLESS it is an object beginning with the term "transform". This should become the new default behaviour. We will fix this in modelRelay initially since this explicitly operates a model based on single transforms anyway.

      Attachments

        Activity

          People

            antranig Antranig Basman
            antranig Antranig Basman
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated: