This package gives you the ability to create synchronization files and prevent you from having to write one time use commands when you've got for example: A database structure change that will require you to synchronize the old structure data with the new structure.
I've got an issue with your package though. I have multiple synchronizations, and when I run the synchronize command it loops through the files from newest to oldest instead of oldest to newest like the migration command. I'm running into an error right now because a newer synchronization relies on an older one. Can you fix this or make a config variable to set the order?
Is your feature request related to a problem? Please describe.
Synchronizations are generally run after migrations. But sometimes a migration needs the synchronization to run correctly. Otherwise you'll get Schema defenitions in synchronizations which should not happen.
Describe the solution you'd like
An option to select a class with --class when running laravel-sync:synchronize to only synchronize one class. This will enable us to use the migration events for up and down to control when a synchronization has to be run.
I was having hard time establishing contact with you through discord , you are a wonderful programmer and we could not progress further without you :( ,
just came here to say you thank you so much for your service and decency.