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

Updated the examples to use the word response instead of res to avoid… #763

Merged
merged 2 commits into from Nov 8, 2019

Conversation

anderslatif
Copy link
Contributor

@anderslatif anderslatif commented Nov 1, 2019

Hi,

I love this library.

The most common use case of using Bcrypt is to hash a password inside of a REST API. The convention for many of these libraries is to use res to indicate response.

I've seen dozens of developers bewildered and collectively wasting hours of debugging because the parameter res overwrites the existing one and the error message given is not clear about this.

All of this can simply be avoided by changing the example to call is response instead of res. Please consider this change.

@recrsn
Copy link
Collaborator

recrsn commented Nov 1, 2019 via email

@anderslatif
Copy link
Contributor Author

@agathver
Thanks for the great suggestion. I've committed again and this time it is result instead of response.

@ncb000gt ncb000gt merged commit bffa114 into kelektiv:master Nov 8, 2019
fast-facts pushed a commit to fast-facts/node.bcrypt.js that referenced this pull request Jun 17, 2022
Updated the examples to use the word response instead of res to avoid…
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.

None yet

3 participants