-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Extract Captcha logic and robot detection to an abstractions library #5932
Conversation
…e.Captcha.Abstractions
hi great. this is what I need. |
Elaborate? |
@Skrypt first of all an erratum: it's an avoidable call to the Robot detection API (IDetectRobot interface) and not ReCaptcha API. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree with the effort of abstracting these services. I will try to review the code to make sure everything is fine. But I think from a first quick glance it looked good.
Please fix the conflicts. |
Conflict fixed :) |
I sincerely apologize for us taking so much time here. I checked out the PR, going over old ones, and this would be quite useful, though with some adjustments, and updated to the latest source. Is this something you'd like to revisit any time soon @chaaboah or should we close? |
This pull request has merge conflicts. Please resolve those before requesting a review. |
Closing due to inactivity. |
Hi there :)
I know this is related to an old issue (#2078) and it was solved by adding an Orchard Core ReCAPTCHA module (pull request #2192).
But i think that extracting the Robot detection and the Captcha behavior, will help the Community to build other Captcha modules with other providers (like hCaptcha who gained popularity thanks to cloudflare).
I'm working on a multi provider Captcha module but it's not ready yet :)
This pull request shouldn't introduce breaking changes, hope my work will help :)
P.S : even if my pull request is rejected i think the method "ProcessAsync" from the RecaptchaTagHelper should be optimized because it has currently an avoidable call to the ReCAPTCHA API