Basics
To use import and export in MoonShine resources, you need to install the dependency via composer
:
composer require moonshine/import-export
Next, to use it in your resource, add the ImportExportConcern
trait and implement the HasImportExportContract
interface.
use MoonShine\ImportExport\Traits\ImportExportConcern;use MoonShine\ImportExport\Contracts\HasImportExportContract; /** * @extends ModelResource<Category> */class CategoryResource extends ModelResource implements HasImportExportContract{ use ImportExportConcern; // ...}
All set! Next, just declare the fields.
Import
Fields
To import, you need to declare the fields in the resource that will participate in the import.
/** * @extends ModelResource<Category> */class CategoryResource extends ModelResource implements HasImportExportContract{ use ImportExportConcern; // ... protected function importFields(): iterable { return [ ID::make(), Text::make('Name'), ]; }}
Be sure to add ID
to the import; otherwise, records will only be added without updating existing ones.
If you need to modify a value during import, you should use the field method fromRaw
.
/** * @extends ModelResource<Category> */class CategoryResource extends ModelResource implements HasImportExportContract{ use ImportExportConcern; // ... protected function importFields(): iterable { return [ ID::make(), Enum::make('Status') ->attach(StatusEnum::class) ->fromRaw(static fn(string $raw, Enum $ctx) => StatusEnum::tryFrom($raw)), ]; }}
Settings
For configuring the import, optional methods are available. To use them, you need to add the import
method that returns ImportHandler
:
protected function import(): ?Handler{ return ImportHandler::make(__('moonshine::ui.import')) // Specify the IDs of users who will be notified when the operation is completed ->notifyUsers(fn(ImportHandler $ctx) => [auth()->id()]) // Select disk ->disk('public') // Select directory for saving the import file ->dir('/imports') // Delete the file after import ->deleteAfter() // CSV delimiter ->delimiter(',') // Modify button ->modifyButton(fn(ActionButton $btn) => $btn->class('my-class')) ;}
If the import()
method returns NULL
, the import button will not be displayed on the index page.
Events
To change the import logic, you can use the model resource events.
public function beforeImportFilling(array $data): array{ return $data;} public function beforeImported(mixed $item): mixed{ return $item;} public function afterImported(mixed $item): mixed{ return $item;}
Export
In the MoonShine admin panel, exporting all data considering the current filtering and sorting can be implemented.
By default, data is exported in xlsx
format, but there is an option to change the format to csv
via the csv()
method of the ExportHandler
class.
Fields
To export, you need to declare the fields in the resource that will participate in the export.
/** * @extends ModelResource<Category> */class CategoryResource extends ModelResource implements HasImportExportContract{ use ImportExportConcern; // ... protected function exportFields(): iterable { return [ ID::make(), Position::make(), Text::make('Name'), ]; }}
If you need to modify a value during export, you should use the field method modifyRawValue
.
/** * @extends ModelResource<Category> */class CategoryResource extends ModelResource implements HasImportExportContract{ use ImportExportConcern; // ... protected function importFields(): iterable { return [ ID::make(), Enum::make('Status') ->attach(StatusEnum::class) ->modifyRawValue(static fn(StatusEnum $raw, Enum $ctx) => $raw->value), ]; }}
Settings
For configuring the export, optional methods are available. To use them, you need to add the export
method that returns ExportHandler
:
protected function export(): ?Handler{ return ExportHandler::make(__('moonshine::ui.export')) // Specify the IDs of users who will be notified when the operation is completed ->notifyUsers(fn() => [auth()->id()]) // Select disk ->disk('public') // Filename ->filename(sprintf('export_%s', date('Ymd-His'))) // Select directory for saving the export file ->dir('/exports') // If you need to export in csv format ->csv() // CSV delimiter ->delimiter(',') // Export with confirmation ->withConfirm() // Modify button ->modifyButton(fn(ActionButton $btn) => $btn->class('my-class')) ;}
If the export()
method returns NULL
, the export button will not be displayed on the index page.
Common methods
ImportHandler
and ExportHandler
extend the base class Handler
, which implements additional methods.
icon
// icon for the buttonicon(string $icon)
queue
// run processes in the backgroundqueue()
modifyButton
// modify buttonmodifyButton(fn(ActionButton $btn) => $btn->class('my-class'))
notifyUsers
// select users for notificationnotifyUsers(fn() => [auth()->id()])
when
// methods by conditionwhen($value = null, callable $callback = null, callable $default = null)
$value
- condition,
$callback
- callback
function that will be executed if the condition is TRUE
,
$default
- callback
function that will be executed if the condition is FALSE
.
//... protected function import(): ?Handler{ return ImportHandler::make('Import') ->when( true, fn($handler) => $handler->delimiter(','), fn($handler) => $handler->delimiter(';') );} //...
unless
// methods by conditionunless($value = null, callable $callback = null, callable $default = null)
$value
- condition,
$callback
- callback
function that will be executed if the condition is FALSE
,
$default
- callback
function that will be executed if the condition is TRUE
.
The unless()
method is the reverse of the when()
method.
Custom implementation
There may be situations where you want to change the import or export implementation. To do this, you need to implement your own class extending ImportHandler
or ExportHandler
.
You can generate the class by using the console command:
php artisan moonshine:handler
After running the command, a base class Handler
will be created in the app/MoonShine/Handlers
directory.
Don’t forget to change the inheritance from Handler
to ImportHandler
or ExportHandler