Can I use Import/Export functionality outside of filament?
We have an app that has export functionality. We roll our own.
Would it be possible to import filament/actions and then to create an Exporter class that is then instantiated and invoked?
Assuming the batches/notifications tables exist along with the filament actions migrations, then I would assume it would all work.
Has anyone tried this? Does anyone know of any reason why this wouldn't work?
Thanks in advance.
Would it be possible to import filament/actions and then to create an Exporter class that is then instantiated and invoked?
Assuming the batches/notifications tables exist along with the filament actions migrations, then I would assume it would all work.
Has anyone tried this? Does anyone know of any reason why this wouldn't work?
Thanks in advance.
