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

refactor(webSocket): rename back to webSocket ala 5.0 #3590

Merged
merged 4 commits into from
Apr 20, 2018

Conversation

benlesh
Copy link
Member

@benlesh benlesh commented Apr 20, 2018

BREAKING CHANGE: UNBREAKING websocket to be named webSocket again, just like it was in 5.0. Now you should import from rxjs/webSocket

BREAKING CHANGE: UNBREAKING websocket to be named `webSocket` again, just like it was in 5.0. Now you should import from `rxjs/webSocket`
Copy link
Collaborator

@jasonaden jasonaden left a comment

Choose a reason for hiding this comment

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

Just need to fix the build.

@benlesh
Copy link
Member Author

benlesh commented Apr 20, 2018

Got it, I didn't update the tsconfig files

@kwonoj
Copy link
Member

kwonoj commented Apr 20, 2018

Error: ENOENT: no such file or directory, lstat '/home/travis/build/ReactiveX/rxjs/src/websocket/package.json'

Build still seems failing, looks related with case sensitivity.

@coveralls
Copy link

Coverage Status

Coverage increased (+0.2%) to 96.708% when pulling 9da773b on benlesh:revert-webSocket-name into f4d7d02 on ReactiveX:master.

@benlesh benlesh merged commit d5658fe into ReactiveX:master Apr 20, 2018
@lock
Copy link

lock bot commented Jun 5, 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 5, 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