Closed (fixed)
Project:
Module Builder
Version:
7.x-2.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
14 Nov 2013 at 16:46 UTC
Updated:
5 Dec 2013 at 21:00 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
siliconmeadow commentedI traced through this and saw that the
$treearray being built appeared to have the key and value pairs swapped, such that it was attempting to use an object for the key and an integer for the value. I didn't push this much harder (but will do). I'm still getting to grips with what the code is actually doing. I see this part of the code is the 'assembling' the tree, but I need to grasp how many types of trees could be assembled and how many could be built in a single build process before I'm convinced that I haven't broken something with this patch.Comment #2
siliconmeadow commentedComment #3
siliconmeadow commentedThis patch does get rid of the error, but then no longer generates the code for the module when used without the
--buildoption.Comment #4
siliconmeadow commentedComment #5
joachim commentedI did a bit of digging. Turns out containingComponent() was returning an object rather than a name.