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

chore(BUILD): fix broken build #3285

Merged
merged 1 commit into from
Feb 1, 2018
Merged

Conversation

benlesh
Copy link
Member

@benlesh benlesh commented Feb 1, 2018

TypeScript seemed to have an issue with XHR all of a sudden, I presume it's some TS update, quick fix any for now to fix the build

TypeScript seemed to have an issue with XHR all of a sudden, I presume it's some TS update, quick fix any for now to fix the build
Copy link
Member

@david-driscoll david-driscoll left a comment

Choose a reason for hiding this comment

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

👍

@benlesh
Copy link
Member Author

benlesh commented Feb 1, 2018

If I had to post mortem this... I'd say it's because TS dictates that all XmlHttpRequest objects MUST have a response property on it, therefor the "else" cases in the two changed lines are (according to TS) never hit. Therefor never.

@rxjs-bot
Copy link

rxjs-bot commented Feb 1, 2018

Messages
📖

CJS: 1365.7KB, global: 731.3KB (gzipped: 118.2KB), min: 141.2KB (gzipped: 30.7KB)

Generated by 🚫 dangerJS

@benlesh benlesh merged commit d487d6b into ReactiveX:master Feb 1, 2018
alexeagle pushed a commit to alexeagle/RxJS that referenced this pull request Mar 2, 2018
TypeScript seemed to have an issue with XHR all of a sudden, I presume it's some TS update, quick fix any for now to fix the build
benlesh pushed a commit that referenced this pull request Mar 2, 2018
TypeScript seemed to have an issue with XHR all of a sudden, I presume it's some TS update, quick fix any for now to fix the build
@lock
Copy link

lock bot commented Jun 6, 2018

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked as resolved and limited conversation to collaborators Jun 6, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants