Support after() on morphs() Columns

[Usmanzahidcode]

Currently, when using $table->morphs('target'), Laravel instantly adds {target}_id and {target}_type columns, without allowing column modifiers like after(). This makes it impossible to control their placement in the table.

Developers often work around this by manually defining both columns with after(), but that defeats the purpose of the morphs() shortcut.

It would be great if morphs() and nullableMorphs() could support column modifiers like after(), making migrations more flexible while keeping the convenience.

Schema::table('posts', function (Blueprint $table) {
    $table->morphs('commentable'); // Cannot use the after() method and other modifiers
});

Schema::table('posts', function (Blueprint $table) {
    $table->unsignedInteger('commentable_id')->after('title');
    $table->string('commentable_type')->after('commentable_id');// Can use the after() method and other modifiers
    $table->index(['commentable_id', 'commentable_type']);
});

[hafezdivandari]

You may try this https://laravel.com/docs/12.x/migrations#column-order

$table->after('title', function (Blueprint $table) {
    $table->morphs('commentable');
});

[Usmanzahidcode]

Shouldn't this be added to the morphs method itself? Or is it avoided to prevent breaking changes during upgrades?

[hafezdivandari]

It can be implemented w/o causing a breaking change, but maybe no one tried sending a PR yet because: 1.there is already a way to do this, 2. Not so easy to implement, 3. high chance of being rejected due to afded value in compare to added lines of code!

[Usmanzahidcode]

Alright, that makes sense. Thank you for the solution, it works.