Skip to content
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

2506 - Added error handling for invalid json responses #2660

Merged
merged 5 commits into from
Nov 6, 2013

Conversation

NTaylorMullen
Copy link
Contributor

}
initialConnectedFired = true;
onSuccess();
tryFailConnect = fireConnect = $.noop;
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think that it is necessary to have tryFailConnect in this assignment. By nulling out onFailed at the end of this function, you are causing tryFailConnect to noop anyway and actually return false. $.noop does not return a value.

Also, can fireConnect ever be fired after tryFailConnect succeeded? If so, onSuccess will still be called which I don't think is right.

NTaylorMullen and others added 5 commits November 5, 2013 15:56
- When an error occurs, instead of throwing ot the window object we now handle it appropriately.

#2506
…rifying parse responses is handled correctly when it throws.

- Also added the wrapStart functionality to the JS test utilities

#2506
- If transports fail to parse a response while in connecting they will now fall back.
- Centralized this logic in the common.js

#2506
…hile connecting indeed do fall back.

- Also fixed some long polling logic

#2506
@NTaylorMullen NTaylorMullen merged commit f7717f7 into release1.1.5 Nov 6, 2013
@NTaylorMullen NTaylorMullen deleted the 2506 branch November 6, 2013 00:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants