docs tweaks

Author: tonysm

docs/conventions.md

@@ -12,6 +12,19 @@ Laravel supports [resource routes](https://laravel.com/docs/controllers#resource
 
 If you don't want to use resource routes, at least consider using the naming convention: render forms in a route name ending in `.create` or `.edit` and name their handler routes ending with `.store` or `.update`.
 
+You may want to define exceptions to the route guessing behavior. In that case, you may want to set the `redirect_guessing_exceptions` in the `config/turbo-laravel.php` config file:
+
+```php
+return [
+    // ...
+    'redirect_guessing_exceptions' => [
+        '/some-page',
+    ],
+];
+```
+
+When using this config, the redirection behavior will still happen, but the package will not guess routes. See the [Validation Response Redirects](/docs/{{version}}/validation-response-redirects) page to know more about why this happens.
+
 ## Partials
 
 You may want to split up your views in smaller chunks (aka. "partials"), such as `comments/_comment.blade.php` which displays a comment resource, or `comments/_form.blade.php` for the form to either create/update comments. This will allow you to reuse these _partials_ in [Turbo Streams](/docs/{{version}}/turbo-streams).

docs/validation-response-redirects.md

@@ -21,7 +21,9 @@ Examples:
 - `comments.store` will guess the form is at the `comments.create` route with no route params.
 - `comments.update` will guess the form is at the `comments.edit` with the `{comment}` param.
 
-If a guessed route name doesn't exist (which will always happen if you don't use the route resorce convention), the middleware will not change the default handling of validation errors. You may also override this behavior by catching the `ValidationException` yourself and re-throwing it overriding the redirect with the `redirectTo` method. If the exception has that, the middleware will respect it and make a GET request to that location instead of trying to guess it.
+If a guessed route name doesn't exist (which will always happen if you don't use the route resource convention), the middleware will not change the default handling of validation errors.
+
+When you're not using the [resource route naming convention](/docs/{{version}}/conventions), you can override redirect behavior by catching the `ValidationException` yourself and re-throwing it overriding the redirect with the `redirectTo` method. If the exception has that, the middleware will respect it and make a GET request to that location instead of trying to guess it.
 
 Here's how you may set the `redirectTo` property:
 
@@ -36,6 +38,19 @@ public function store()
 }
 ```
 
+You may want to have exceptions to the route guessing behavior, which you can use the `redirect_guessing_exceptions` config in the `config/turbo-laravel.php` config file:
+
+```php
+return [
+    // ...
+    'redirect_guessing_exceptions' => [
+        '/some-page',
+    ],
+];
+```
+
+The internal redirect will still happen, but the resource route convention will not be used.
+
 ## Turbo HTTP Middleware
 
 The package ships with a middleware which applies some conventions on your redirects, specially around how failed validations are handled automatically by Laravel. Read more about this in the [Conventions](#conventions) section of the documentation.