-
29 Sep 2012 5:48 PM #1
Sencha Cmd 3 Dependency Ordering Issue
Sencha Cmd 3 Dependency Ordering Issue
It appears that the compilation process is not handling requires in app.js correctly. For example, my app has a requires for Ext.data.* in app.js and I then have a model class that is using a hasMany association (Ext.data.association.HasMany). In this scenario, the resulting ordering is as follows:
My model - 40,763
Ext.define('Ext.data.association.HasMany') - 123,626
Ext.application from app.js - 134,297
If I add a requires for HasMany directly in my model class, then there's no problem.
I am on build 3.0.0.181. I'm not sure whether this is a unique issue or the same as this one:
http://www.sencha.com/forum/showthre...s-out-of-order
-
29 Sep 2012 7:16 PM #2
Thanks for the report! I have opened a bug in our bug tracker. It looks different than the original issue plus that was fixed in 3.0.0.181.
Success! Looks like we've fixed this one. According to our records the fix was applied for
SDKTOOLS-175
in
3.0.0 Sprint 7.


Reply With Quote