Implementing AUTH_MODEL for Import & Export Enhancement

[SupianIDz]

Today I was confused when using the database on QUEUE_CONNECTION Import & Export Job always failed, after I investigated because \App\Models\User was not found.

FYI: I'm using \App\Domains\User\Models\User

Should we use AUTH_MODEL instead of forcing bind User model to Illuminate\Contracts\Auth\Authenticatable on ServiceProvider in Import & Export ?

Or add this in the Documentation?

see :

filament/packages/actions/src/Exports/Models/Export.php

Lines 52 to 56 in 68e4a11

	if (! class_exists(\App\Models\User::class)) {
	throw new Exception('No [App\\Models\\User] model found. Please bind an authenticatable model to the [Illuminate\\Contracts\\Auth\\Authenticatable] interface in a service provider\'s [register()] method.');
	}
	return $this->belongsTo(\App\Models\User::class);

filament/packages/actions/src/Imports/Models/Import.php

Lines 58 to 62 in 68e4a11

	if (! class_exists(\App\Models\User::class)) {
	throw new Exception('No [App\\Models\\User] model found. Please bind an authenticatable model to the [Illuminate\\Contracts\\Auth\\Authenticatable] interface in a service provider\'s [register()] method.');
	}
	return $this->belongsTo(\App\Models\User::class);

[Ercogx]

I also do not understand why binding is needed and not to take the value from the config, I have not seen such use in other libraries

[ProgrammerZ]

I found it strange to bind to Authenticatable. I believe a configuration setting would be a better approach, and even better if it defaults to pulling Authenticatable Model from authGuard() config and also custom config if different from default authGuard().

Also consider issue with app(Router::class)->middlewareGroup('filament.actions', ['web', 'auth']); when using non standard guard like['auth:admin']