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
Accounts.forgotPassword and Accounts.verifyEmail throw error instead of pass error in callback #5664
Comments
I guess there is a bit of distinction of a runtime error that can't be predicted, vs. a programming error where the argument is of the wrong type. In an ideal world, these arguments could be statically checked. However, I'd definitely accept a PR for returning these errors through the callback instead of throwing them. |
Thanks @stubailo, that sounds fun. Is there a guide to submitting a pull-request? Which branch do I clone from, and pull-request to? Can I link it to this issue? Is there automated tests to extend? |
Unfortunately there isn't a great guide about it. But basically:
|
Thanks for the good directions :) I found some similar info in Contributing-to-Meteor but your steps are more useful. |
Hi @stubailo, I've had fun: cloned the repo, created a new local branch from devel, patched the file, created two tests that pass, and filled in the contributors form. I tried creating a pull request from github desktop, no permission to publish ... same if I try to push the new branch. Do I need to fork into another github repo just to do a pull request? |
Yes, you can only do a pull request on github from a fork, which is kind of On Wed, Nov 18, 2015 at 7:44 PM Misha Verplak notifications@github.com
|
Fixed in #7117! |
Where the email address is blank, or the token is blank, the methods throw a new error, but the docs say they return errors in the callback.
The bad thing about this is undocumented behaviour, plus needing two forms of error handling.
Code in: meteor/packages/accounts-password/password_client.js
The text was updated successfully, but these errors were encountered: