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
It would be nice and more aligned with how the [Migration Order](../tree/master/readme.md#Migration Order) natively works in Laravel, to have an Attribute automatically created, containing the date of the migration creation:
Note
Each migration filename contains a timestamp that allows Laravel to determine the order of the migrations
useBastinald\LaravelAutomaticMigrations\Attributes\MigrationScaffoldedAt;
class MyModel extends Model
{
#[MigrationScaffoldedAt('2024_01_10_123456')]
publicfunctionmigration(Blueprint$table)
{
$table->id();
$table->string('name');
$table->timestamp('created_at')->nullable();
$table->timestamp('updated_at')->nullable();
}
}
This would then be implemented something like this:
It would be nice and more aligned with how the [Migration Order](../tree/master/readme.md#Migration Order) natively works in Laravel, to have an
Attribute
automatically created, containing the date of the migration creation:Note
Each migration filename contains a timestamp that allows Laravel to determine the order of the migrations
This would then be implemented something like this:
The text was updated successfully, but these errors were encountered: