Update migration stub and existing migrations to use anonymous class

docs/content/1_docs/3_modules/12_nested-modules.md

@@ -68,13 +68,13 @@ Route::get('{slug}', function ($slug) {
 })->where('slug', '.*');
 ```
 
-For more information on how to work with nested items in your application, you can refer to the 
+For more information on how to work with nested items in your application, you can refer to the
 [laravel-nestedset package documentation](https://github.com/lazychaser/laravel-nestedset#retrieving-nodes).
 
 ### Setting a maximum nested depth
 
 You can also define the maximum depth allowed for the module changing the following:
-```php 
+```php
 protected $nestedItemsDepth = 1;
 ```
 Note: a depth of 1 means parent and child.
@@ -100,23 +100,20 @@ We'll use the `slug` and `position` features in this example but you can customi
 
 ```
 php artisan twill:make:module issues -SP
-php artisan twill:make:module issueArticles -SP --parentModel=Issue 
+php artisan twill:make:module issueArticles -SP --parentModel=Issue
 ```
 
 Add the `issue_id` foreign key to the child module's migration:
 
 ```php
-class CreateIssueArticlesTables extends Migration
+public function up()
 {
-    public function up()
-    {
-        Schema::create('issue_articles', function (Blueprint $table) {
-            // ...
-            $table->foreignIdFor(Issue::class);
-        });
-
+    Schema::create('issue_articles', function (Blueprint $table) {
         // ...
-    }
+        $table->foreignIdFor(Issue::class);
+    });
+
+    // ...
 }
 ```
 
@@ -137,7 +134,7 @@ class IssueArticle extends Model implements Sortable
         // ...
         'issue_id',
     ];
-    
+
     public function issue()
     {
         return $this->belongsTo(Issue::class);

docs/content/1_docs/4_form-fields/11_repeater.md

@@ -179,19 +179,16 @@ php artisan twill:make:module TeamMember -P
   relationship:
 
 ```php
-class CreateTeamMembersTables extends Migration
+public function up()
 {
-    public function up()
-    {
-        Schema::create('team_members', function (Blueprint $table) {
-            /* ... */
-
-            $table->foreignId('team_id')
-                ->constrained()
-                ->onUpdate('cascade')
-                ->onDelete('cascade');
-        });
-    }
+    Schema::create('team_members', function (Blueprint $table) {
+        /* ... */
+
+        $table->foreignId('team_id')
+            ->constrained()
+            ->onUpdate('cascade')
+            ->onDelete('cascade');
+    });
 }
 ```
 
@@ -306,5 +303,3 @@ of the repeater items. This directive also accepts a `hidePrefix` option to hide
     :required="true"
 />
 ```
-
-

docs/content/1_docs/7_media-library/05_custom-metadata.md

@@ -1,6 +1,6 @@
 # Custom metadata
 
-By default, media comes with a few metadata attributes that can be filled in from the media managers: 
+By default, media comes with a few metadata attributes that can be filled in from the media managers:
 Tags, Alt text and caption.
 
 Say we want to add more metadata, some of which might be translatable. To do this we have to go through a few
@@ -41,7 +41,7 @@ use Illuminate\Database\Migrations\Migration;
 use Illuminate\Database\Schema\Blueprint;
 use Illuminate\Support\Facades\Schema;
 
-class AddFieldsToMedia extends Migration
+return new class extends Migration
 {
     public function up()
     {
@@ -58,7 +58,7 @@ class AddFieldsToMedia extends Migration
             $table->dropColumn('attribution');
         });
     }
-}
+};
 ```
 
 And that is all. The most important part is to make sure your migration fields are named the same as your custom metadata values in the twill config.

docs/content/2_guides/1_page-builder-with-blade/4_creating-the-page-module.md

@@ -129,7 +129,7 @@ We can see that `Route::module('pages');` has been added to `routes/twill.php`.
 
 This is automatic, because it is simple enough to do.
 
-The `routes/twill.php` file is a Twill specific list of routes. These routes are protected and loaded specifically for 
+The `routes/twill.php` file is a Twill specific list of routes. These routes are protected and loaded specifically for
 the CMS.
 
 In standard Laravel there is no `module` method on a `Route` object, this is something Twill provides and it will build
@@ -139,7 +139,7 @@ many routes for your module, these are then used by the cms, controllers and req
 
 The second step, we have to do ourself. So let's open `app/Providers/AppServiceProvider.php`.
 
-We will not go into detail about what a service provider is, for that you can check the 
+We will not go into detail about what a service provider is, for that you can check the
 [official documentation](https://laravel.com/docs/10.x/providers).
 
 In our `boot` method we will add the suggested snippet:
@@ -214,14 +214,14 @@ use Illuminate\Database\Migrations\Migration;
 use Illuminate\Database\Schema\Blueprint;
 use Illuminate\Support\Facades\Schema;
 
-class CreatePagesTables extends Migration
+return new class extends Migration
 {
     public function up()
     {
         Schema::create('pages', function (Blueprint $table) {
             // this will create an id, a "published" column, and soft delete and timestamps columns
             createDefaultTableFields($table);
-            
+
             // add those 2 columns to enable publication timeframe fields
             // (you can use publish_start_date only if you don't need to provide the ability to specify an end date)
             // $table->timestamp('publish_start_date')->nullable();
@@ -250,7 +250,7 @@ class CreatePagesTables extends Migration
         Schema::dropIfExists('page_slugs');
         Schema::dropIfExists('pages');
     }
-}
+};
 ```
 
 This file will create the minimum required tables and columns that Twill uses to provide the CMS functionality. Later in

docs/content/2_guides/1_page-builder-with-blade/9_adding-navigation.md

@@ -62,7 +62,7 @@ use Illuminate\Database\Migrations\Migration;
 use Illuminate\Database\Schema\Blueprint;
 use Illuminate\Support\Facades\Schema;
 
-class CreateMenuLinksTables extends Migration
+return new class extends Migration
 {
     public function up()
     {
@@ -83,7 +83,7 @@ class CreateMenuLinksTables extends Migration
     {
         Schema::dropIfExists('menu_links');
     }
-}
+};
 ```
 
 Now you can run the migration: `php artisan migrate`
@@ -223,7 +223,7 @@ use App\Models\MenuLink;
 class MenuLinkRepository extends ModuleRepository
 {
     protected $relatedBrowsers = ['page'];
-    
+
     use HandleNesting;
 
     public function __construct(MenuLink $model)
@@ -367,7 +367,7 @@ We will change the contents of `resources/views/components/menu.blade.php` to th
 ```
 
 We add just a minimal amount of styling as we will not spend too much time on that during this guide. But this will
-build a navigation tree that is slightly indented so that you can see the proper structure. 
+build a navigation tree that is slightly indented so that you can see the proper structure.
 
 You cannot see it in action yet, for that we have to add the component to the main template file.
 
@@ -389,7 +389,7 @@ But, for this guide, we will simply open `resources/views/site/page.blade.php` a
 </head>
 <body>
 <x-menu/> <!-- [tl! ++] -->
-<div class="mx-auto max-w-2xl">
+<div class="max-w-2xl mx-auto">
     {!! $item->renderBlocks() !!}
 </div>
 </body>
@@ -402,4 +402,3 @@ Wherever you will put `<x-menu/>` it will render the menu. That's useful because
 Now that we have pages and a menu, we have one last thing we need to do.
 
 [We need a frontpage](./10_setup-the-frontpage.md)!
-

docs/content/2_guides/json_repeaters/migration.php

@@ -4,7 +4,7 @@
 use Illuminate\Database\Schema\Blueprint;
 use Illuminate\Support\Facades\Schema;
 
-class CreateProjectsTables extends Migration
+return new class extends Migration
 {
     public function up()
     {
@@ -20,4 +20,4 @@ public function down()
     {
         Schema::dropIfExists('projects');
     }
-}
+};

docs/content/2_guides/manage_frontend_user_profiles_from_twill/2021_08_01_204153_create_profiles_tables.php

@@ -3,7 +3,7 @@
 use Illuminate\Database\Migrations\Migration;
 use Illuminate\Database\Schema\Blueprint;
 
-class CreateProfilesTables extends Migration
+return new class extends Migration
 {
     public function up()
     {
@@ -27,4 +27,4 @@ public function down()
     {
         Schema::dropIfExists('profiles');
     }
-}
+};

docs/content/2_guides/prefill-block-editor-from-template/2021_09_19_131244_create_articles_tables.php

@@ -3,7 +3,7 @@
 use Illuminate\Database\Migrations\Migration;
 use Illuminate\Database\Schema\Blueprint;
 
-class CreateArticlesTables extends Migration
+return new class extends Migration
 {
     public function up()
     {
@@ -31,4 +31,4 @@ public function down()
         Schema::dropIfExists('article_slugs');
         Schema::dropIfExists('articles');
     }
-}
+};

examples/portfolio/database/migrations/2022_04_01_071515_create_projects_tables.php

@@ -4,7 +4,7 @@
 use Illuminate\Database\Schema\Blueprint;
 use Illuminate\Support\Facades\Schema;
 
-class CreateProjectsTables extends Migration
+return new class extends Migration
 {
     public function up(): void
     {
@@ -34,4 +34,4 @@ public function down(): void
         Schema::dropIfExists('project_slugs');
         Schema::dropIfExists('projects');
     }
-}
+};

examples/portfolio/database/migrations/2022_04_01_071748_create_partners_tables.php

@@ -6,7 +6,7 @@
 use Illuminate\Database\Schema\Blueprint;
 use Illuminate\Support\Facades\Schema;
 
-class CreatePartnersTables extends Migration
+return new class extends Migration
 {
     public function up(): void
     {
@@ -44,4 +44,4 @@ public function down(): void
         Schema::dropIfExists('partner_slugs');
         Schema::dropIfExists('partners');
     }
-}
+};

examples/portfolio/database/migrations/2022_04_06_070334_create_comments_tables.php

@@ -4,7 +4,7 @@
 use Illuminate\Database\Schema\Blueprint;
 use Illuminate\Support\Facades\Schema;
 
-class CreateCommentsTables extends Migration
+return new class extends Migration
 {
     public function up(): void
     {
@@ -21,4 +21,4 @@ public function down(): void
     {
         Schema::dropIfExists('comments');
     }
-}
+};

examples/portfolio/database/migrations/2022_05_30_074255_create_links_tables.php

@@ -4,7 +4,7 @@
 use Illuminate\Database\Schema\Blueprint;
 use Illuminate\Support\Facades\Schema;
 
-class CreateLinksTables extends Migration
+return new class extends Migration
 {
     public function up(): void
     {
@@ -23,4 +23,4 @@ public function down(): void
     {
         Schema::dropIfExists('links');
     }
-}
+};

examples/tests-browsers/database/migrations/2021_08_10_0001_create_writers_tables_for_browsers.php

@@ -3,7 +3,7 @@
 use Illuminate\Database\Migrations\Migration;
 use Illuminate\Database\Schema\Blueprint;
 
-class CreateWritersTablesForBrowsers extends Migration
+return new class extends Migration
 {
     public function up()
     {
@@ -23,4 +23,4 @@ public function down()
         Schema::dropIfExists('writer_revisions');
         Schema::dropIfExists('writers');
     }
-}
+};

examples/tests-browsers/database/migrations/2021_08_10_0002_create_letters_tables_for_browsers.php

@@ -3,7 +3,7 @@
 use Illuminate\Database\Migrations\Migration;
 use Illuminate\Database\Schema\Blueprint;
 
-class CreateLettersTablesForBrowsers extends Migration
+return new class extends Migration
 {
     public function up()
     {
@@ -23,4 +23,4 @@ public function down()
         Schema::dropIfExists('letter_revisions');
         Schema::dropIfExists('letters');
     }
-}
+};

examples/tests-browsers/database/migrations/2021_08_10_0003_create_letter_writer_table_for_browsers.php

@@ -3,7 +3,7 @@
 use Illuminate\Database\Migrations\Migration;
 use Illuminate\Database\Schema\Blueprint;
 
-class CreateLetterWriterTableForBrowsers extends Migration
+return new class extends Migration
 {
     public function up()
     {
@@ -19,4 +19,4 @@ public function down()
     {
         Schema::dropIfExists('letter_writer');
     }
-}
+};

examples/tests-browsers/database/migrations/2021_08_10_0004_create_bios_tables_for_browsers.php

@@ -3,7 +3,7 @@
 use Illuminate\Database\Migrations\Migration;
 use Illuminate\Database\Schema\Blueprint;
 
-class CreateBiosTablesForBrowsers extends Migration
+return new class extends Migration
 {
     public function up()
     {
@@ -25,4 +25,4 @@ public function down()
         Schema::dropIfExists('bio_revisions');
         Schema::dropIfExists('bios');
     }
-}
+};

examples/tests-browsers/database/migrations/2021_08_10_0005_create_books_tables_for_browsers.php

@@ -3,7 +3,7 @@
 use Illuminate\Database\Migrations\Migration;
 use Illuminate\Database\Schema\Blueprint;
 
-class CreateBooksTablesForBrowsers extends Migration
+return new class extends Migration
 {
     public function up()
     {
@@ -23,4 +23,4 @@ public function down()
         Schema::dropIfExists('book_revisions');
         Schema::dropIfExists('books');
     }
-}
+};