FLUID-3045: fluid.initSubcomponents() should probably throw an Error if the type of the subcomponent has not been properly defined in the parent component's options

Metadata

Source
FLUID-3045
Type
Bug
Priority
Major
Status
Closed
Resolution
Fixed
Assignee
Justin Obara
Reporter
Colin Clark
Created
2009-07-16T15:49:18.000-0400
Updated
2014-03-03T14:26:45.120-0500
Versions
  1. 0.6
  2. 0.7
  3. 0.8
  4. 1.0
  5. 1.1
  6. 1.1.1
  7. 1.1.2
  8. 1.2
Fixed Versions
  1. 1.5
Component
  1. Framework

Description

At the moment, if a type isn't defined for a subcomponent within its parent's options, initSubcomponent() returns undefined. Any attempt to call the resulting subcomponent will of course cause an error. Perhaps we should explicitly throw an error?

Here's a snippet of the implementation:

fluid.initSubcomponents = function (that, className, args) {
var entry = that.options[className];
if (!entry) {
return;
}

Comments

  • Colin Clark commented 2010-03-30T19:18:01.000-0400

    This issue is filed against 1.5 because it is largely a concern for the new IoC system.

  • Antranig Basman commented 2013-05-25T05:39:51.419-0400

    The current implementations of "fluid.initSubcomponents" as well as "fluid.initDependent" will indeed throw an error if no type is defined for the component. fluid.initSubcomponent itself and related functions will be deprecated for Fluid 1.9 and removed for Fluid 2.0