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

Error generated by MockClient isn't the same as the real one #58

Open
digitalcora opened this issue Mar 12, 2020 · 0 comments
Open

Error generated by MockClient isn't the same as the real one #58

digitalcora opened this issue Mar 12, 2020 · 0 comments
Labels
Milestone

Comments

@digitalcora
Copy link

digitalcora commented Mar 12, 2020

Normally an "invalid-input-response" error from reCAPTCHA causes the verify function to return {:error, [:invalid_input_response]}. However, when using the feature of the MockClient where the response "invalid_response" intentionally causes an error, the return is instead {:error, [:"invalid-input-response"]}. If you have different handling for different reCAPTCHA errors, the consequence is that you have to match on the "fake error" separately from the real one.

@samueljseay samueljseay added the bug label Jul 7, 2021
@samueljseay samueljseay added this to the 4.0.0 milestone Jul 7, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants