This documentation is currently being moved to our new documentation site.
Please view or edit the documentation there, instead.
If you're looking for Fluid Project coordination, design, communication, etc, try the Fluid Project Wiki.
_demands spec format
The demands specification object can occur in a few forms:
Recommended:
| the string name of the creator function for the demanding subcomponent. |
| an object specifying how the |
| an IoC-resolved reference (most likely of the form { |
any pseudoargument name | The name of any pseudoargument defined by the grade of the component which is to be created, representing the slot of a positional argument in the transformed argument list |
Alternative:
| the string name of the creator function for the demanding subcomponent. |
| an IoC-resolved reference (most likely of the form { |
| an array of objects composing the |
any pseudoargument name | The name of any pseudoargument defined by the grade of the component which is to be created, representing the slot of a positional argument in the transformed argument list |
mergeOptions
is a rarely-used alternative to options
. It may be useful in cases where a user wants to write a single demands block, yet have several values merged together in a particular sequence if the demands block acts.
Note that mergeOptions
and options
are mutually exclusive: Use one or the other, but not both.
Alternative:
| the string name of the creator function for the demanding subcomponent. |
| array of parameters to the function, or a single argument. |
Note: If the args
record is used, NONE of the other mentioned elements can be present (none of options
, mergeOptions
, container
, etc.).
Alternative:
| array of parameters to the function, or a single argument. |
In this case, the funcName
entry is interpreted as being empty.