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

add socket.io v1.7.1 & update auto-update config #9791

Merged
merged 2 commits into from Dec 6, 2016

Conversation

pvnr0082t
Copy link
Contributor

Pull request for issue: #9772
@x09326 @kennynaoh Please help me review this pull request, thank you.

  • add latest version of socket.io
  • update auto-update config due to the file structure changed after v1.7.0

close #9772

@@ -12,10 +12,9 @@
"npmName": "socket.io-client",
Copy link
Contributor

Choose a reason for hiding this comment

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

@pvnr0082t
Uh...I think this is the right npmName.
How do you think?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

@x09326 but the npm auto-update config added in 4cce6db. It use socket.io-client.

Copy link
Contributor

Choose a reason for hiding this comment

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

@PeterDaveHello
Is this is the right npmName?

Copy link
Contributor

Choose a reason for hiding this comment

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

Isn't it? Is there a the reason for not right?

Copy link
Contributor

Choose a reason for hiding this comment

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

socket.io-client looks correct for me

Copy link
Contributor

@x09326 x09326 Dec 5, 2016

Choose a reason for hiding this comment

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

Because socket.io-client in npm directing to github repo is this.
Maybe we can modify the name and repository of this lib to socket.io-client, I think that will be better.
Or it will confuse socket.io with socket.io-client.

Copy link
Contributor

Choose a reason for hiding this comment

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

nope, socker.io it's the main repo, we host its client.

Copy link
Contributor

Choose a reason for hiding this comment

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

btw, we could never change the lib name, it'll break the current users.

@x09326
Copy link
Contributor

x09326 commented Dec 5, 2016

LGTM

1 similar comment
@kennynaoh
Copy link
Contributor

LGTM

@kennynaoh kennynaoh assigned PeterDaveHello and unassigned kennynaoh and x09326 Dec 5, 2016
@PeterDaveHello
Copy link
Contributor

not at all since it needs rebase ...

@pvnr0082t
Copy link
Contributor Author

@x09326 @kennynaoh I have rebased it on the latest master branch. Please help me review it again, thank you.

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.

[Request] socket.io v1.7.0 and v1.7.1
4 participants