Add configurable default id type for schema builder

[mohamedsharaf]

Description

This PR introduces a new static property on the schema Builder to configure the default column type used by $table->id().

Currently, $table->id() always produces a bigIncrements column. This is fine for many applications, but more and more projects default to UUID or ULID for their primary keys. Today, the only way to achieve that is to either:

• Manually call $table->uuid('id')->primary() or $table->ulid('id')->primary() in every migration, or
• Register a custom Blueprint macro in each project.

Changes in this PR

• Added Builder::$defaultIdType (similar to the existing Builder::$defaultMorphKeyType).
• Default remains bigIncrements for full backwards compatibility.
• Supported values: bigIncrements, uuid, ulid.

When changed, $table->id() will respect this global default.

Example

use Illuminate\Database\Schema\Builder;

// Globally set default id type for migrations
Builder::$defaultIdType = 'ulid';

Now, any migration that calls:

Schema::create('users', function (Blueprint $table) {
    $table->id(); // ULID by default
});

Will produce:

create table `users` (
    `id` char(26) not null primary key
);

Motivation

• Provides consistency with $defaultMorphKeyType.
• Simplifies migrations for teams using UUID/ULID.
• Keeps migration files cleaner and more expressive without boilerplate.

Backward Compatibility

• The default remains bigIncrements, so no breaking changes.
• Existing migrations and behavior remain unchanged unless developers explicitly configure Builder::$defaultIdType.

Community Tip

If you want all of your migrations to default to ULID or UUID primary keys, you can configure this once in your AppServiceProvider

use Illuminate\Database\Schema\Builder;

/**
 * Bootstrap any application services.
 */
public function boot(): void
{
    // Use ULIDs as default id type
    Builder::$defaultIdType = 'ulid';

    // Or, if you prefer UUIDs:
    // Builder::$defaultIdType = 'uuid';
}

Now, every $table->id() call in your migrations will automatically create the correct column type without needing to repeat $table->uuid('id')->primary() or $table->ulid('id')->primary() everywhere.

[github-actions]

Thanks for submitting a PR!

Note that draft PR's are not reviewed. If you would like a review, please mark your pull request as ready for review in the GitHub user interface.

Pull requests that are abandoned in draft may be closed due to inactivity.

[shaedrich]

Are you sure, you didn't accidentally merge the wrong branch into yours?

[shaedrich]

It would be nice if you could narrow this further down

Suggested change

	* @var string
	* @var 'int'|'uuid'|'ulid'

[shaedrich]

Maybe, this could be handled via an Enum

[shaedrich]

Even though, it's done similarly with the default morph column type and the mapping to big integer mostly makes sense, what if, for some reason, someone can not or doesn't want to use the non-big integer type?

[shaedrich]

Why no ULID?

[shaedrich]

You could add some error handling here

Suggested change

	if (Builder::$defaultIdType === 'uuid') {
	return $this->uuid($column)->primary();
	} elseif (Builder::$defaultIdType === 'ulid') {
	return $this->ulid($column)->primary();
	}
	return $this->bigIncrements($column);
	return match (Builder::$defaultIdType) {
	'uuid' => $this->uuid($column)->primary(),
	'ulid' => $this->ulid($column)->primary(),
	'id' => $this->bigIncrements($column),
	default => throw new InvalidArgumentException("Key type must be 'int', 'uuid', or 'ulid'."),
	};

[shaedrich]

Your indention is off here

Suggested change

	return $this->uuid($column)->primary();
	} elseif (Builder::$defaultIdType === 'ulid') {
	return $this->ulid($column)->primary();
	return $this->uuid($column)->primary();
	} elseif (Builder::$defaultIdType === 'ulid') {
	return $this->ulid($column)->primary();

[crynobone]

Need to fix merge conflict.

[donnysim]

Won't this break third party migrations?