Bug in Loader code?

[mark0978]

Ext version tested:

• Ext 4.0.7

Browser versions tested against:

• FireFox 8, Chrome 16.0.912.63 m

DOCTYPE tested against:

• html

Description:

• I should mention that I have YET to get ext-dev.js to run my app, this is the ONLY error message I get though and it appears to be spurious. If it isn't, please let me know what I should be doing here.
• I get this error message while using ext-dev.js:
• Uncaught Ext.Error: The following classes are not declared even if their files have been loaded: ''. Please check the source code of their corresponding files for possible typos: ''
• The class being loaded is always Ext.data.writer.Writer

Steps to reproduce the problem:

• Load my app?

The result that was expected:

• No error message

The result that occurs instead:

• See description

Test Case:
In onFileLoaded, the code in bold should be added to prevent this spurious warning (I think).

...
                if (missingClasses.length < 1) {
                    return;
                }


                missingClasses = Ext.Array.filter(missingClasses, function(item) {
                    return !this.requiresMap.hasOwnProperty(item);
                }, this);


                if (missingClasses.length < 1) { // This code is missing
                    return;
                }


               for (i = 0,ln = missingClasses.length; i < ln; i++) {
                    missingPaths.push(this.classNameToFilePathMap[missingClasses[i]]);
                }
...

[mitchellsimoens]

This is usually due to a misspelling of the class name versus file name.

[mark0978]

But in this case, the name is '' and the file it is having trouble with is Ext.writer.Writer which I don't explicitly use.

Look at the code I included, it looks to see if there are any missingClasses, then it removes all the ones that currently exist and NEVER checks to see if there are still missing Classes....... it just raises the error.

And My code does work with ext-all-debug.js

[evant]

Your stuff will always work with ext-all-debug, because it includes every class. From looking at the code, it loops over the missing classes, so if the length is 0, then it won't push any missing path on, so the second check would be redundant.

You'll need to post a test case, but I don't think this looks like a bug.