Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.


  • In general, transformations pass their result one level up, unless "outputPath" is explicitly given

This implies that the transform system at the moment has just two parsing states - 


  • As for "undefined input" - there seems to be a wide class of transforms for which "undefined input" implies that the transform is inactivated and produces no output. For example every conventional "value mapping" transform like fluid.linearScale is like this. However there seem to be some transforms which are special - fluid.condition when receiving undefined as its condition input treats it as "false". We should vet all the transforms that we have to make sure we understand what all these cases are and can document them as global rules.