You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Would be good for each generator, but at least for a specific resource - that would look for migration, model, controller and routes and delete them if found. Especially useful since the "resources" generator currently creates and runs the migration. See the other isse I reported.
The text was updated successfully, but these errors were encountered:
Rolling back any action is not a simple problem, it's like writting a mini VCS just for the generated/modified files.
I guess there are mostly two cases in which you will need a rollback:
You accidently generated something you don't need. You mostly need to just delete the files/lines added by the generators.
If you generated a migration that was applied, you will need to rollback migrations first, remove it, run composer dump-autoload, then re-apply migrates.
You accidentally typed something wrong. You simply rerun the command with --force=true. Again if there was a migration, you should rollback migrations and delete the wrong one manually before re-running the command.
Would be good for each generator, but at least for a specific resource - that would look for migration, model, controller and routes and delete them if found. Especially useful since the "resources" generator currently creates and runs the migration. See the other isse I reported.
The text was updated successfully, but these errors were encountered: