diff --git a/context.md b/context.md index 76bd2d01bf..8c95bde587 100644 --- a/context.md +++ b/context.md @@ -56,7 +56,7 @@ Log::info('User authenticated.', ['auth_id' => Auth::id()]); The written log will contain the `auth_id` passed to the log entry, but it will also contain the context's `url` and `trace_id` as metadata: -``` +```text User authenticated. {"auth_id":27} {"url":"https://example.com/login","trace_id":"e04e1a11-e75c-4db3-b5b5-cfef4ef56697"} ``` @@ -96,7 +96,7 @@ class ProcessPodcast implements ShouldQueue The resulting log entry would contain the information that was added to the context during the request that originally dispatched the job: -``` +```text Processing podcast. {"podcast_id":95} {"url":"https://example.com/login","trace_id":"e04e1a11-e75c-4db3-b5b5-cfef4ef56697"} ``` diff --git a/dusk.md b/dusk.md index 004ad6b641..b92e230897 100644 --- a/dusk.md +++ b/dusk.md @@ -234,8 +234,8 @@ By default, this trait will truncate all tables except the `migrations` table. I * @var array */ protected $tablesToTruncate = ['users']; - ``` + Alternatively, you may define an `$exceptTables` property on your test class to specify which tables should be excluded from truncation: ```php diff --git a/filesystem.md b/filesystem.md index d50402e30f..0a586523bc 100644 --- a/filesystem.md +++ b/filesystem.md @@ -99,7 +99,7 @@ composer require league/flysystem-aws-s3-v3 "^3.0" --with-all-dependencies An S3 disk configuration array is located in your `config/filesystems.php` configuration file. Typically, you should configure your S3 information and credentials using the following environment variables which are referenced by the `config/filesystems.php` configuration file: -``` +```ini AWS_ACCESS_KEY_ID= AWS_SECRET_ACCESS_KEY= AWS_DEFAULT_REGION=us-east-1 diff --git a/http-tests.md b/http-tests.md index 29a978a680..8ad87f6920 100644 --- a/http-tests.md +++ b/http-tests.md @@ -514,7 +514,6 @@ test('asserting an exact json match', function () { 'created' => true, ]); }); - ``` ```php tab=PHPUnit diff --git a/pennant.md b/pennant.md index f158490a59..d85ee7781a 100644 --- a/pennant.md +++ b/pennant.md @@ -1178,7 +1178,6 @@ public function boot(): void { Event::listen(UnexpectedNullScopeEncountered::class, fn () => abort(500)); } - ``` ### `Laravel\Pennant\Events\FeatureUpdated` diff --git a/pulse.md b/pulse.md index e129001bfc..2ebf1bb460 100644 --- a/pulse.md +++ b/pulse.md @@ -476,13 +476,13 @@ PULSE_DB_CONNECTION=pulse By default, Pulse will store entries directly to the [configured database connection](#using-a-different-database) after the HTTP response has been sent to the client or a job has been processed; however, you may use Pulse's Redis ingest driver to send entries to a Redis stream instead. This can be enabled by configuring the `PULSE_INGEST_DRIVER` environment variable: -``` +```ini PULSE_INGEST_DRIVER=redis ``` Pulse will use your default [Redis connection](/docs/{{version}}/redis#configuration) by default, but you may customize this via the `PULSE_REDIS_CONNECTION` environment variable: -``` +```ini PULSE_REDIS_CONNECTION=pulse ``` diff --git a/redirects.md b/redirects.md index a4fbf8772d..884ff8d39d 100644 --- a/redirects.md +++ b/redirects.md @@ -14,8 +14,8 @@ Redirect responses are instances of the `Illuminate\Http\RedirectResponse` class Route::get('/dashboard', function () { return redirect('/home/dashboard'); }); - ``` + Sometimes you may wish to redirect the user to their previous location, such as when a submitted form is invalid. You may do so by using the global `back` helper function. Since this feature utilizes the [session](/docs/{{version}}/session), make sure the route calling the `back` function is using the `web` middleware group or has all of the session middleware applied: ```php diff --git a/reverb.md b/reverb.md index 49f2d3e60a..8dd0ed34a6 100644 --- a/reverb.md +++ b/reverb.md @@ -29,7 +29,7 @@ You may install Reverb using the `install:broadcasting` Artisan command: -``` +```shell php artisan install:broadcasting ```