Demands block observation

Antranig Michael Basman antranig.basman at Colorado.EDU
Tue Mar 19 19:13:59 UTC 2013

"mergeOptions" has much more limited use than before, but it is still 
not completely without value. It may be that a user wants to write a 
single demands block, yet have several values merged together in a 
particular sequence if the demands block acts. The only way to achieve 
this effect would be through the use of "mergeOptions". I can't think of 
a realistic use case for this feature, but given we had some 
implementation left over I thought we may as well leave this as a 
"feature remnant". The partner directive "mergeAllOptions" has been removed.


On 19/03/2013 17:12, Cheetham, Anastasia wrote:
> Antranig, I wanted to double-check on the status of 'mergeOptions' in the demands specification.
> It isn't used much, but the docs describe it as follows:
> 	"an array of objects composing the options argument to a component's creator function
> 	 is to be assembled by merging several different IoC-resolved records together."
> It's quite possible I'm not correctly understanding what that means, but it seems to me that 'mergeOptions' is not really necessary anymore, now that FLUID-4130 has been addressed and options merging is now supported in demands blocks. Is this correct?

More information about the fluid-work mailing list