-
Notifications
You must be signed in to change notification settings - Fork 23
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
Inconsistencies with promise.js #16
Comments
Feel free to do a PR |
I plan to. Would it be alright to change the name of |
What would be the benefit? It would be a breaking change |
Maybe we could leave |
I think the promise wrapper used to be the same API as the callback API, just returning promises. Is that not the case anymore? If not, in what version was it changed? |
I believe the point of the wrapper is to have the same API, but it is currently not the case. There are some things missing, some things that don't belong in you current definitions. Could you check https://github.com/sidorares/node-mysql2/blob/master/promise.js and let me know what you think? Thank you. |
Not sure what you want me to look for? |
The differences from your definitions. Like the examples I've given. |
I haven't used MySQL in a very long time, multiple years now. I don't have time to aggregate the differences, but will happily accept a PR if you wanna bring it up-to-date |
No problem. Do you want to keep the name |
I would try to avoid breaking changes if possible, so I don't see a reason to rename it (it's just an interface and the implementation is not exported) |
I haven't looked much into this, but
promise.d.ts
defines aConnection
interface with achangeUser
method, but https://github.com/sidorares/node-mysql2/blob/master/promise.js definesPromiseConnection
with a different structure. I noticed this when I got a run-time error stating myConnection
object had nochangeUser
method.This
PromiseConnection
is what is returned fromcreateConnection
.https://github.com/sidorares/node-mysql2/blob/master/promise.js does not define a
createUser
method, but you do have access to the underlyingConnection
.The text was updated successfully, but these errors were encountered: