New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
big fat batch of changes #97
Conversation
…cces function to cleanup timeout and make sure complete is also run.
…node test (test gives error on multiple cookies)
Conflicts: reqwest.js
@@ -1,7 +1,8 @@ | |||
.PHONY: boosh test | |||
|
|||
boosh: | |||
node_modules/smoosh/bin/smoosh make build.json | |||
@node -e "var json = require('./build');json.JSHINT_OPTS=JSON.parse(require('fs').readFileSync('./.jshintrc'));require('fs').writeFileSync('./build.json', JSON.stringify(json, null, 2))" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
keep build.json and .jshintrc consistent.
try { | ||
ok(err && err.status === 0, 'correctly caught timeout') | ||
} catch (e) { | ||
ok(true, 'IE is a troll') |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this is for the can't touch properties on aborted xhr
in IE thing. caveat emptor, not our problem.
most of the rest of the changes are either reformatting or @bartsidee's original changes |
I don't remember where this is at so I'm just going to press the merge button and cross my fingers. |
HAHAHAHAHHAA |
Pulled in #96 then got caught in a death-spiral of JSHint, reformatting and fixing bugs and tests for other (and older) browsers; some recent tests were obviously just targeting Chrome.
Submitting as a PR rather than just merging cause it's kind of major and you might want to have a browse over it @ded.
Will comment inline.