-
22 Oct 2011 3:22 PM #1
Ext.app.Controller bug in getModuleClassName ?
Ext.app.Controller bug in getModuleClassName ?
I'm not sure but I think there is a bug in getModuleClassName. this.name should be namespace.
Code:getModuleClassName: function(name, type) { var namespace = Ext.Loader.getPrefix(name); if (namespace.length > 0 && namespace !== name) { return name; } return this.name + '.' + type + '.' + name; // IS THIS A BUG? // Shouldn't it be: return namespace +'.' + type + '.' + name; },
-
31 Oct 2011 11:11 AM #2Sencha - Sencha Touch Dev Team
- Join Date
- Mar 2007
- Location
- Redwood City, California
- Posts
- 3,653
- Vote Rating
- 14
Thank you for the report.
-
11 Dec 2011 5:07 PM #3
Now same thing in Ext.app.Application [PR3]
Now same thing in Ext.app.Application [PR3]
Looking at this in PR3, getModuleClassName() is no longer in Ext.app.Controller, but has been moved to Ext.app.Application. But has exact same definition as what was classified here as a bug.
Other thing that looks fishy is that Ext.app.Controller appears to be aliased to Ext.Application. Beginning of Ext.app.Controller is as follows:Code:getModuleClassName: function(name, type) { var namespace = Ext.Loader.getPrefix( name ); if (namespace.length > 0 && namespace !== name) { return name; } return this.name + '.' + type + '.' + name; }
Perhaps some hasty "cut-n-paste" refactoring??Code:Ext.define( 'Ext.app.Controller', { alternateClassName: 'Ext.Application'
-
15 Dec 2011 3:27 PM #4Sencha - Community Support Team
- Join Date
- Jan 2009
- Location
- Palo Alto, California
- Posts
- 1,941
- Vote Rating
- 6
This has all been reworked for PR4. I'm closing the ticket because it works in a different way internally now
Ext JS Senior Software Architect
Personal Blog: http://edspencer.net
Twitter: http://twitter.com/edspencer
Github: http://github.com/edspencer
Looks like we can't reproduce the issue or there's a problem in the test case provided.


Reply With Quote