fluid-tech IRC Logs-2013-08-26

fluid-tech IRC Logs-2013-08-26

[16:22:37 CDT(-0500)] <yzen> hi Bosmon

[16:26:43 CDT(-0500)] <Bosmon> yzen!

[16:27:01 CDT(-0500)] <yzen> Bosmon: so I'm trying out the wrapper removal in kettle

[16:27:02 CDT(-0500)] <Bosmon> ZENE'EVICH!

[16:27:07 CDT(-0500)] <Bosmon> yzen - excellent

[16:27:20 CDT(-0500)] <yzen> all my tests pass but one

[16:27:34 CDT(-0500)] <Bosmon> Very promising

[16:27:46 CDT(-0500)] <yzen> Bosmon: this reference does not get resolved : https://github.com/fluid-project/kettle/blob/master/lib/dataSource.js#L67

[16:28:06 CDT(-0500)] <yzen> you can see the relation to data source within this component and the one above (the data source itself)

[16:29:03 CDT(-0500)] <Bosmon> yzen - don't see any reason it shouldn't be resolved

[16:29:05 CDT(-0500)] <Bosmon> Might well be a bug

[16:29:34 CDT(-0500)]

<yzen> Bosmon: exact error: Assertion failure (see console.log for expanded message): Failed to resolve reference

Unknown macro: {kettle.dataSource}

.options.responseParser - could not match context with name kettle.dataSource from component leaf ,[object Object]

[16:29:57 CDT(-0500)] <yzen> it;s a little bit complicated though

[16:30:05 CDT(-0500)] <Bosmon> yzen - that looks like a different site

[16:30:09 CDT(-0500)] <Bosmon> I thought we were looking at modelParser

[16:30:10 CDT(-0500)] <yzen> because i m using a promiseDataSource that has kettle.dataSource grade

[16:30:41 CDT(-0500)] <yzen> no

[16:30:41 CDT(-0500)] <yzen> data source

[16:30:41 CDT(-0500)] <yzen> which it's parent comopnent

[16:30:53 CDT(-0500)] <Bosmon> You highlighted line 67

[16:30:56 CDT(-0500)] <Bosmon> Which is inside modelParser

[16:33:07 CDT(-0500)] <yzen> Bosmon: yes but the reference is to a data source compnent

[16:33:22 CDT(-0500)] <yzen> now imagine if data source component is used as a grade

[16:33:27 CDT(-0500)] <yzen> that's when it fails

[16:33:37 CDT(-0500)] <Bosmon> Well ok - perhaps it would be better to see the example rather than imagining

[16:35:03 CDT(-0500)] <Bosmon> Anyway, "I see no reason why this shouldn't work" .... it may well be a bug of some kind