with debugAtAllCosts: true, a json answer turns to true

[guest]

I send a request like that : var bindArgs = {

url: someUr;, load: function(type, data, evt) {

makeSthWith(data);

}, mimetype: "text/json"

}; var req = dojo.io.bind(bindArgs);

when debugAtAllCosts: true, "data" is a boolean with "true" value, whereas it should be a list.

[James Burke]

Trying this test with debugAtAllCosts set to true seems fine with JSON responses (Dojo 0.4.2): tests/io/test_BrowserIO.json.html

Closing the bug for now, but feel free to reopen with a more complete test case and describe what type of build are you using (xdomain ajax build, regular widget build, etc..)

[guest]

I add a test case. So if you add debugAtAllCosts: true, the list of files are not created, as it returns true from the server. Example of what the server must return for one list : ["RNGtoHTMLform.xsl","RNGtoHTMLform_standalone.xsl"]

[sjmiles]

You've neglected the required call to dojo.hostenv.writeIncludes().

Please refer to the debugAtAllCosts documentation here: ​http://manual.dojotoolkit.org/WikiHome/DojoDotBook/Book122

[(none)]

Milestone 0.4.3 deleted