You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+7-7Lines changed: 7 additions & 7 deletions
Original file line number
Diff line number
Diff line change
@@ -347,19 +347,19 @@ Create your form in index.blade.php:
347
347
348
348
Go to /index and click submit button on contact us form and you should see an error message that 'Score does not meet the treshhold' because the threshold >2. You can play around the controller to see all outcomes. Importantly, you need to wait the script to be loaded before clicking the submit button.
349
349
350
-
###Vue Usage <aname="vue-usage" />
350
+
## Vue Usage <aname="vue-usage" />
351
351
352
352
The package provides a lightweight vue component. You need to publish the vue component before playing around it.
The Blade way is no longer useful if you use Vue, so we need to manage to assign site key by ourselves. The component supports props below:
365
365
@@ -378,7 +378,7 @@ Supported: siteKey, elementId, inline and action, check the original file to see
378
378
379
379
There are two ways you can bind reCAPTCHA v3 to the component, in the following example, you need to import GoogleReCaptchaV3 component first and then pass site key into the component.
380
380
381
-
######Use prop
381
+
### Use prop
382
382
383
383
````vue
384
384
<template>
@@ -437,7 +437,7 @@ There are two ways you can bind reCAPTCHA v3 to the component, in the following
437
437
438
438
````
439
439
440
-
######Add site key directly into GoogleReCaptchaV3 component
440
+
### Add site key directly into GoogleReCaptchaV3 component
441
441
442
442
Alternatively, I believe most of cases your site key will never be changed, so you could just modify the original published component to have sitekey hard-coded in.
443
443
@@ -469,7 +469,7 @@ Remove it from prop and add it in data():
469
469
470
470
## Advanced Usage <aname="advanced-usage" />
471
471
472
-
####Custom implementation on Config
472
+
### Custom implementation on Config
473
473
474
474
For some users, they might store the config details in their own storage e.g database. You can create your own class and implement:
475
475
@@ -486,7 +486,7 @@ Remember to register it in your own service provider
486
486
);
487
487
```
488
488
489
-
####Custom implementation on Request method
489
+
### Custom implementation on Request method
490
490
491
491
The package has two default options to verify: Guzzle and Curl, if you want to use your own request method, You can create your own class and implement
0 commit comments