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

make connect/open/openSet/disconnect return a promise, fixes #3622 #3790

Merged
merged 1 commit into from
Jan 24, 2016
Merged

Conversation

TrejGun
Copy link
Contributor

@TrejGun TrejGun commented Jan 24, 2016

No description provided.

@vkarpov15 vkarpov15 added this to the 4.4 milestone Jan 24, 2016
@vkarpov15
Copy link
Collaborator

Thanks 🍻

Btw how's the discussion going over at expressjs/express#2844 ? Looks like you stirred up a hornet's nest over there :)

vkarpov15 added a commit that referenced this pull request Jan 24, 2016
make connect/open/openSet/disconnect return a promise, fixes #3622
@vkarpov15 vkarpov15 merged commit 367ac15 into Automattic:master Jan 24, 2016
@TrejGun
Copy link
Contributor Author

TrejGun commented Jan 25, 2016

hehe, you are welcome

I'm not really participating in there. As for me Doug should give a f**k to IBM and its managers whos can bring to the express only one thing - bureaucracy. Fork the project and maintain it as before, instead he removed expressjs/express repo :( so may be my next project will be on koa.

@vkarpov15
Copy link
Collaborator

Tried using koa but I'm not really a fan yet. I'm sticking with express for now, but also considering forking because of fear of bureaucracy.

@Starefossen
Copy link

mongoose@4.4.0 completely broke my production systems because of this change. Why was this not considered a major version change? If not, what is the versioning of Mongoose releases?

@vkarpov15
Copy link
Collaborator

@Starefossen because AFAIK this shouldn't be backwards breaking - the old callback approach should still work. How did this break your system?

@Starefossen
Copy link

This line results in can not call function "on" on undefined error when upgrading to v4.4.0.

@vkarpov15
Copy link
Collaborator

You're right, sorry for the oversight. Will push a 4.4.1 fix for this today.

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.

3 participants