FLUID-4144: MergePaths does not resolve the "{options}" element during IOC demands resolution.

Metadata

Source
FLUID-4144
Type
Bug
Priority
Critical
Status
Closed
Resolution
Fixed
Assignee
Justin Obara
Reporter
y z
Created
2011-03-14T17:07:02.849-0400
Updated
2014-03-03T13:13:40.574-0500
Versions
  1. 1.4
Fixed Versions
  1. 1.5
Component
  1. IoC System

Description

When demands block contains the mergePaths policy for merging component options with demands options further component creation will not handle the resulting options argument to the creator function correctly.

Sample demands block:

fluid.demands("uploader", "cspace.recordEditor", ["{recordEditor}.dom.uploader", {
mergePaths: ["{options}", {
model: "{recordEditor}.model",
applier: "{recordEditor}.options.applier"
}]
}]);

as a result "{options}" will end up in that.options.value... instead of the correct that.options

Comments

  • Antranig Basman commented 2012-05-23T16:11:35.241-0400

    "mergePaths" contains many implementation flaws and will be abolished completely when FLUID-4130 lands. It is probably not worth fixing the implementation in its current form.

  • Antranig Basman commented 2013-02-19T14:52:08.252-0500

    Resolved by merge of FLUID-4330 branch at revision 91d5d1