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

[chore/MSSDK-2051]: Update readme with info about Google reCAPTCHA #468

Merged

Conversation

pawelacio
Copy link
Collaborator

Description

combine what? and why?

Updates

shortly about how? you implemented the solution -
either a few lines of technical summary or bullet points

Screenshots

Testing

Additional Notes

@pawelacio pawelacio marked this pull request as ready for review February 24, 2025 11:39
@Saddage Saddage added the chore Used for chores that help maintain the codebase. Updates patch version of the package on release. label Feb 24, 2025
@pawelacio pawelacio merged commit 2721d59 into feat/MSSDK-1993-google-recaptcha Feb 24, 2025
3 checks passed
@pawelacio pawelacio deleted the chore/MSSDK-2051-update-readme branch February 24, 2025 12:56
Saddage added a commit that referenced this pull request Feb 25, 2025
* Feat/MSSDK-2048: Add Google reCAPTCHA into Register flow (#443)

* feat/MSSDK-2048: Add google recaptcha into Register flow

* feat/MSSDK-2048: Changes after CR

* [Feat/MSSDK-2050]: Add configuration method (#444)

* feat/MSSDK-2048: Add google recaptcha into Register flow

* feat/MSSDK-2048: Changes after CR

* feat/MSSDK-2050: Add configuration method for Google reCAPTCHA

* feat/MSSDK-2050: Fix sonarcube error

* feat/MSSDK-2050: Remove logging

* fix/MSSDK-2050: fix the ReCaptcha not being triggered (#445)

* chore/MSSDK-2050: add debugging logs for recaptcha in register form

* chore/MSSDK-2050: add debugging logs for recaptcha in register form

* chore/MSSDK-2050: add debugging logs for recaptcha in register form

* chore/MSSDK-2050: add debugging logs for recaptcha in register form

* chore/MSSDK-2050: add debugging logs for recaptcha in register form

* chore/MSSDK-2050: add debugging logs for recaptcha in register form

* chore/MSSDK-2050: add debugging logs for recaptcha in register form

* chore/MSSDK-2050: add debugging logs for recaptcha in register form

* chore/MSSDK-2050: add debugging logs for recaptcha in register form

* fix/MSSDK-2050: commit cleaned up code with the final fix

* chore/MSSDK-2050: add debugging logs

* chore/MSSDK-2050: add debugging logs

* chore/MSSDK-2050: add debugging logs

* chore/MSSDK-2050: add debugging logs

* chore/MSSDK-2050: add debugging logs

* chore/MSSDK-2050: add debugging logs

* chore/MSSDK-2050: add debugging logs

* chore/MSSDK-2050: clean up code for code review

* chore/MSSDK-2050: recreate pnpm-lock

* chore/MSSDK-2050: remove the isolated prop - needs confirmation if we would like to use this

* feat/MSSDK-2049: captcha challenge in purchase flow (#447)

* feat/MSSDK-2049: captcha challenge in purchase flow

* feat/MSSDK-2049: add missing prepare script

* feat/MSSDK-2049: fix deprecated husky command

* feat/MSSDK-2049: fix deprecated husky command

* feat/MSSDK-2049: add unit tests for the new recaptcha hook

* feat/MSSDK-2112: Add errors for google recaptcha (#452)

* feat/MSSDK-2112: Add errors for google recaptcha

* feat/MSSDK-2112: Update after CR

* fix/MSSDK-2112: Fix behaviour if challange called (#453)

* fix/MSSDK-2133: Fix invalid token error nad small refactor (#459)

* [chore/MSSDK-2051]: Update readme with info about Google reCAPTCHA (#468)

* chore/MSSDK-2051: Update readme with info about Google reCAPTCHA config method

* chore/MSSDK-2051: Update link to docs

* chore/MSSDK-2051: Update readme with optional values

* feat/MSSDK-1993: empty commit to bump GH actions

---------

Co-authored-by: Paweł Kaczmarek <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
chore Used for chores that help maintain the codebase. Updates patch version of the package on release.
Development

Successfully merging this pull request may close these issues.

2 participants